Re: Prototypes in Module Source

Rory Hewitt wrote:

I have to agree with you - I've never liked coding DEFINEs in my program
source - I like to be able to simply code COPYs. Plus, I like the fact that
if you have a separate prototype copybook, you can include lots of comments
about *how* the procedure should be called, possible return values etc.,
whilst leaving the actual procedure code as a black-box. This is especially
true for shipped software.

I use separate files for prototypes etc too, but if I _was_ going to use the same file, I'd code all the /copy stuff at the top, with all the nice comments etc. Then I'd code the real module after the /copy stuff, and have it copy itself in when it needed the prototypes.

Denis, if you use this mechanism with SQL, you have to specify RPGPPOPT(*LVL1), or *LVL2, on the CRTSQLRPGI.

*---------------------------------------------
* M o d u l e i n t e r f a c e
*---------------------------------------------
/if defined(prototypes_only)

/if defined(mymodule_h)
/eof
/endif
/define mymodule_h

[prototypes, constants, data structure templates etc]

/eof
/endif

*---------------------------------------------
* M o d u l e i m p l e m e n t a t i o n
*---------------------------------------------
H keywords
Ffiles
/define prototypes_only
/copy mymodule
D more definitions
etc