Re: RPG400-L Digest V3 #291

[Jon.Paris@xxxxxx]

 >> So in fact you are saying "Don't use EXTPROC", which has nothing to do
with whether the called procedure uses a procedure interface or not.

Jeez Joep - did you actually _read_ what I said?  I didn't say any such
thing.

If a PI/PR is used when compiling a module and the ExtProc keyword is used
in the PR then that is the name that is exported for the procedure -
regardless of the name of the module.  _Without_ ExtProc the exported name
is always the uppercase version of the proto name or module name if no
proto is used.

So if ExtProc is used on the proto in the calling program, and the called
program used a *Entry PList you must make sure the name is in upper case.

If the called procedure uses a PR/PI combination instead of the *Entry then
the case of the name in the ExtProc doesn't matter as long as caller and
callee both use the same capitalization.

In the examples below, if the proto shown is included in the called
procedure then the exported name will be 'PROGRAMA' and either proto can be
used in the caller.  In the third example the exported name will be
'ProgramA' and only that exact ExtProc can be used in the caller.

     D ProgramA        Pr
     D ProgramA        Pr                  ExtProc('PROGRAMA')

     D ProgramA        Pr                  ExtProc('ProgramA')

Jon Paris
Jon.Paris@e400.com

www.e400.com - A new wave of iSeries and AS/400 Education

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