Re: Compiler directive

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

You have a common procedure named core_CrackPath. It takes an IFS path
and cracks it into its directory path, file name and file extension
parts. That procedure belongs in the COREPROCS srvpgm and its
prototype is found in the PRCORE srcmbr. Whenever a module contains
code that calls the core_CrackPath proc, that module has to include
the PRCORE srcmbr.

It's more when you get to prototyping external programs as a
replacement for *ENTRY PLIST and CALL PARM garbage.

I am simplifying when I say the PR srcmbr is for the srvpgm.  What I
do is have the application being the center of the universe. There is
one PR srcmbr for the application. There is also one SRVPGM for the
application. Since programs are part of an applications, all the PR
prototypes of the programs are located in the PR srcmbr of the
application.  The PR srcmbr of the application then contains
constants, likeds data structs, procedure prototypes and program
prototypes.

The rule still holds. The module includes all the PR srcmbrs of the
procedures and programs that it directly calls.

-Steve