Re: Prototypes in Module Source

On 21/03/2008, at 3:27 AM, Bruce Guetzkow wrote:

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.

This is a dumb idea. I think an iSeries News author (perhaps Julian Moneypenny?) first used this technique. It's clumsy, cumbersome, ugly, confusing, non-standard, horrible, etc. etc. etc. See my other comments today on Midrange-L.

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.

I see Scott has shown an example. Search iSeries News for more. By all means investigate the approach then avoid it.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------