Re: Compiler directive

Lim Hock-Chai wrote:

So, you would not oppose to create a master prototype copy book that
include all the service programs' prototype copy books?  If so, is there
any cons to include this master prototype copy book in all programs?

If including a master prototype copy book would bring in tons of
irrelevant procedures, then I think some division is probably useful.

If a particular module is only supposed to be managing a linked list of
data structures, should it really copy in the prototypes of all the
procedures that handle tax calculations?  Having procedures readily
available is good if they are the kind of procedures that can be called
from anywhere, but it's probably good to have some impediment to calling
irrelevant procedures.

I guess we've seen two extremes - one extreme that requires an explicit
/copy or /define for every procedure that will be called, and one
extreme that gives access to any procedure ever written.  I think
somewhere in-between is right; the exact place in-between depends on
your situation.