RE: Memory Layout

>>CALLP and use a prototype -
problem disappears!
I work in a world of RPGII, RPGIII,RPGIV,RPGILE(agree with u on new apps.),
all Mixed together.

>> After all - right or wrong it is what the called program defines
the parm as that matters - not the callers view of it.
"compares parms along the way." Would not comparing check called to callers?

Sorry just a "Redneck" programmer. Can do it, just can't say it.:)

Bill H.

-----Original Message-----
From: Jon Paris [mailto:Jon.Paris@Partner400.com]
Sent: Monday, September 16, 2002 1:36 PM
To: rpg400-l@midrange.com
Subject: Memory Layout


 >> Might be a good tool to write. Follows call path and compares parms
along the way.

Why bother?  Convert the CALLs and CALLBs to CALLP and use a prototype -
problem disappears!

It might be worth the effort of developing a tool that examines all *ENTRY
PLISTs and determines what parms are expected and then build the prototypes
from that.  After all - right or wrong it is what the called program defines
the parm as that matters - not the callers view of it.

Jon Paris
Partner400

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