Re: Compiler directive

Lim Hock-Chai wrote:

Let me be a bit more specific:

Let say I've a program that needs to use proc1 and proc3 of MYSVC
service program, the first method will allow me to copy just the proc1
and proc3 prototypes that I needed but it requires three line of code to
do the copy:

/Define proc1
/Define proc3
/Include Qrpglesrc,MYSVCPRO

The second method only requires one statement but the proc2 prototype
will also be included:
/Include Qrpglesrc,MYSVCPRO

Any pros and cons for the above two?

A con for the 3-line version is that it makes it more cumbersome to use
the procedures that are available through that /copy.  To call a
procedure, you have to go up to the /copy line, see if it's already been
used, and if not, code your /Define.  It might sufficient to stop a
programmer from calling a procedure if they thought that it would only
require a few lines of code to just do whatever the procedure does
without bothering to call it.

Much more convenient to just be able to use the available procedures
freely.

I'm not suggesting that the entire set of all possible procedures be
available with a single /copy; just that once you have decided to use a
particular set of procedures, you should be able to get them all just by
coding the /copy.