MI builtins

Regarding the new MI list, I assume that "MI" means both "old" MI programs
and the use of new MI builtin functions in ILE programs: "The MI400 Mailing
List is for AS/400 technicians to discussion programming of the Machine
Interface level of the AS/400.".

I'm not sure that everyone understands the concept of "builtin function".
When you "call" an RPG or MI builtin, the compiler or translator conversion
your call into specialized code.  In most cases, the code required to
provide that function will be generated directly into the code.  In the
case of RPG builtins, the RPG compiler does it.  In the case of MI
builtins, it is the translator that generates the special code for the
builtin.

The upshot of this is that a builtin function "call" often doesn't require
a call at all.

The nice thing about the ILE "call" interface to the MI builtins (C, RPG,
COBOL whatever) is that you don't really have to worry about portability,
as long as you understand what the builtin does.  If you port to a platform
that doesn't have that builtin function, you just write your own procedure
to do the same thing as part of porting.  As long as your procedure has the
same call interface as the builtin, you shouldn't have to change any
calling code.

Barbara Morris


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---