× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Just some thoughts on this:

How are you certain that this (overloaded) procedure getName will return the 
correct name? If two procedures expect a numeric value and you pass a numeric 
value, will the first procedure not accept the "call" and return its found 
name? the similar problem applies to character values. Just wondering.

And on the topic of syntax checking:
Can any one tell me a modern free formatted programming language that does 
syntax checking while entering code? I cannot think of any. So, if none can be 
mentioned, then we were spoilt while coding in fixed format.

Regards,
Carel Teijgeler.


*********** REPLY SEPARATOR  ***********

On 15-10-03 at 13:17 Buck wrote:

>> You think procedure overloading is anywhere even
>> CLOSE to a necessity in **business application** design??
>
>Here is one business function where I would find overloading useful.
>Imagine a function called getName.  I want to get my Vendor name, Customer
>name, Employee name, G/L account name, Company name, Division name, etc.
>Each of those files has a different key; some character, some numeric.
>Different sizes too.  It'd be nice to have such a feature where I could just
>eval name=getName(whatEverKey) as opposed to the current requirement that I
>create a uniquely named procedure for each file.  I don't think of this as
>particularly object oriented, but it's useful for exchanging data with other
>companies,in old EDI format as well as XML.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.