Re: Using procedure prototypes and interfaces instead *ENTRY PLIST

["Joe Teff" <jteff19@xxxxxxx>]

> Note that this is a PROCEDURE definition. However, in this example we're
> not defining parameters for a PROCEDURE, rather we're defining
> parameters for a PROGRAM.

this I know, no need to SHOUT

> The ExtPgm keyword thus indicates we're defining parameters for a
> program. In this case, the very program with the procedure prototype,
> hence these are entry parameters.

I've only thought of this as a value for a calling program, and not for a
called program. I understand your point now. Thanks.

> Gary Guthrie
> Editor, The RPG Source at http://www.news400.com/TheRPGSource
> 
> > Joe Teff wrote:
> > 
> >       D EntryParms      PR                  ExtPgm('TEST')
> >       D  Trailer                      10
> >       D  SCACCode                     10
> >       D EntryParms      PI
> >       D  Trailer                      10
> >       D  SCACCode                     10
> > 
> > I don't understand the ExtPgm('TEST') part. As this is acting
> > like a *ENTRY PLIST, why would you put the ExtPgm keyword
> > on it? I understand why this would be for the calling program,
> > but not the called pgm.


+---
| 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
+---