Re: Prototypes in Module Source

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

I think it is better to maintain these function prototypes in separate 
members, with an appropriate wrapper of  /IF DEFINED(membername) ... and 
/ENDIF to prevent accidentally /COPYing the same member definitions more 
than once.

Then, the real main-line code also /COPYs this same member for the 
actual definition of the external procedure interfaces. That way, you 
know that the actual compiled code (service program or *PGM) always 
matches the external definition as defined in the corresponding /COPY 
member.

> Bruce Guetzkow wrote:
> All:
>
> I know I've seen this done before but after 30 minutes of searching through
> the archives I can't find it...
>
> 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.
>
> Can someone share some sample code that I can review?  I'm considering doing
> this for a new application I'm working on, but want to see how involved it
> is to make it work before I decide on a direction.  If there is an example
> in the archives (and I'm sure there is, but since I can't even manage to
> work the fax machine today...), please just point me there and I'll stare at
> it for a while.
>
> Thanks in advance,
> --Bruce Guetzkow
>
>
>
>