Re: Compiler directive

On 8/7/06, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:

<snip>
     /IF NOT DEFINED(copybook-name)
     /DEFINE(copybook-name)
copybook data goes here
     /ENDIF
</snip>

You know, that may even look cleaner that what we currently are doing. Our
main programs have:
     /If not defined(JOBI0200)
     /INCLUDE ROUTINES/QAPISRC,JOBI0200
     /EndIf
When they simply could have
     /INCLUDE ROUTINES/QAPISRC,JOBI0200
And then the member JOBI0200 could have:
     /If not defined(JOBI0200)
     // ... all the stuff that JOBI0200 currently has...
     /EndIf
And we wouldn't have to retrofit our current main programs.
And if someone wrote a main program and forgot the /IF they wouldn't get
burned.

either method looks confusing.  Do people use /if defined to bring in
code or prototypes?  Instead of conditionally compiling code I prefer
to have the code exist in service program procedures.  And instead of
conditionally including prototypes it is easier for me to have one PR
source member for each service program. Then the module being compiled
simply includes the PR source members of the service programs it will
be calling into.  I find that even 5000 line PR source members compile
fairly quickly.  Not the question, but bottom line is I recommend
against conditional compilation.

-Steve