RE: Benefits of Sub-procedures

["Bob cozzi" <cozzi@xxxxxxxxx>]

Joe,
That is correct, and why would you not put the names in there anyway?
Cloning? Don't you think its more beneficial to be able to see what the
procedure name is of the procedure above the one your looking at by seeing
the ending P spec with the proc name on it vs. just an empty "P" sitting
there? Besides, doesn't your IDE have a Procedure Wizard in it to generate
subprocedures and their prototypes for you?  CodeStudio does.  :)


Bob Cozzi
Cozzi Consulting
www.rpgiv.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Friday, October 24, 2003 10:28 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Benefits of Sub-procedures

> From: Barbara Morris
> 
> Andy, you can write your program to /copy in the prototype and use a
> procedure interface instead of the *ENTRY PLIST.  Then you get the
same
> parameter checking as with procedures.

I'm very close to this today, Barbara.  I'd like to replace *ENTRY PLIST
with prototypes.  From what I can find on the list, that's as easy as:

1. Create a prototype using EXTPGM in a /copy
2. Include that in both calling and called programs
3. Use a PI with the name of the program in the called program

Now, I have a minor issue with this.  Right now, I have stopped labeling
PI statements (and the procedure end statements).  Instead, the only
place I specify the name of a procedure is in the procedure begin
statement.  This seems to be fine syntactically, and it replaces a lot
of ugly drudgework when cloning prototypes.

But it seems that in this case, I MUST use the name in the PI statement.

Am I understanding this stuff correctly?

Joe


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.