Re:

[Gary Guthrie <GaryGuthrie@xxxxxxxx>]

Hi Barbara,

For tutorial purposes I find that it's sometimes clearer to somebody
trying to learn something to see it as it will be built by the copy
function anyhow. The point I was trying to make was how to move entry
parameters to the D-specs rather than how to code for modularity. In the
real world, yes, when it makes sense for modular reasons to place things
in a copy member one should do so. This is often the case for
prototypes. In MY real world, I do indeed place prototypes and
interfaces in copy members. 

With respect to your comment that if one did place them in a copy member
they'd need to change the name on both the PR and the PI, I'm presuming
you mean to prevent duplicate names. I hope I didn't inadvertently imply
that no matter what and in all cases EntryParms should be the name
supplied on all procedure prototypes used for entry parameters. I was
just using it as a clear tutorial, pointing out that it could be
anything but that I chose EntryParms for more intuitive understanding of
the example.

Jim was provided with many comments such as

        Don't use the cycle
        Don't use UPDATE, use EXCEPT
        Create a logical so as not to read all records
        Use CONST because the program doesn't change the parameters
        Etc...

It seemed to me that Jim had just selected some quick and easy code for
some RPG IVesque commentary. I didn't think he wanted us to give him
everything there was to give with respect to RPG and design!

Gary Guthrie
Editor, The RPG Source at http://www.news400.com/TheRPGSource


> That's fine if this program is never intended to be called by another RPG
> program.  But if it is, you will want to move the prototype into a /COPY file,
> and then you'll have to change the name on both the PR and the PI.  I'd change
> "EntryParms" to a name that a CALLP user would want to use.
+---
| 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
+---