Re: mi access to a dtaara

["Larry Loen" <lwloen@xxxxxxxxxx>]

>2nd example. Chgs and additions to the api.  As400 adds addn parms to its
>api, adds another rtn fmt name ( objd0100, objd0200, ... ) when it adds a
>new feature to its api.  This makes the api increasing more complex to
use.
>Some parms are ignored, others must be set to a specific value, ...   In
the
>class/mbr paradigm, when an api gets a new feature, a new mbr function is
>added to the class. No chg to the original mbr function. The os knows
which
>one is being called based on the nbr of arguments passed, the types of
these
>arguments.

Both your examples (especially this one) relies on having a language where
the arguments form part of the "signature" that is supported by the linkage
process explicitly.  This is one of the great features of C++.  It is,
however, not an enforcable feature of at least C and probably not a great
many other languages even in the Microsoft world.  Most historical
languages link only to the "method" name (function name in historical
terms).

Maybe in 2001 this is a great idea, but part of the reason OS/400 APIs are
as they are is that they work will languages old and new.  It certainly
creates the problem you cite, but it also allows people to code in their
own familiar language (say, RPG) and not have to buy a compiler they
otherwise would not need (say, in some shops, C++).


Larry W. Loen  -   Senior Java and iSeries Performance Analyst
                          Dept HP4, Rochester MN


+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---