RE: Prototypes in Module Source

<snip>
I am currently keeping RPGLE procedure prototypes in a separate source
file
member (QCPYSRC) and using /copy in both the procedure source and the
caller
to bring in the prototypes for compiling. I have seen people use
compiler
directives to keep the prototype directly in the procedure source and
/copy
the procedure source into the caller. Based on the directives the
caller
only sees the prototypes.
</snip>

This could be done using if defines but why would you want to do it?
Also, the need for a separate QCPYSRC.

I use a single source file QSRCF for everything and prototypes are
identified by a "_PR" on the end. Bindery by "_B". Only have to go to
one place.

XVERRH Top level binder
XVERRH_PR Prototypes
XVERRH_B Bindery
XVERRH_M01 Module one
XVERRH_M02 Module two
XVERRH_M03 Module three

One big problem I could see with doing this is what happens when you
have multiple modules? I want my prototypes to be in a separate member
so when I want to look at the interface for a procedure, I can just look
at one thing, not the entire program. If you put the prototypes in the
modules, you are going to have to know which module contains which
procedures. Sounds very confusing to me. If I had three different
modules, I would have to put three different /copy in the program and
you are still going to have a separate member for the bindery.

Anyway, my opinion only.