RE: Prototypes in Module Source

David,

I'm in the separate /COPY member camp.

However, I second Jerry's comment that having a single procedure per prototype member is a bad idea.

I also recommend wrapping the prototypes in /IF DEFINED, I use a combination of the examples Rory and
Barbara gave...my prototype /COPY members start out like so:

/if defined (CVCONTROL_INCD)
/eof
/endif
/define CVCONTROL_INCD

This way, I'm protected against accidentally coping in the same info twice; As some of my /COPY
members include their own /COPY statements to bring in DS or field templates.

HTH,

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of David FOXWELL
Sent: Wednesday, March 26, 2008 5:12 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Prototypes in Module Source

Hi everyone,

I've found this thread rather difficult to follow but here goes.

I think you are debating using how to pull in the prototype source for the
compiler from either 1, the source from another module, or 2, a source
member containing just the prototypes.

In 1, I need to use /DEFINE. In 2, I just use /COPY. Tell please me if
I've misunderstood.

We want to do away with /DEFINE. We're looking at putting a prototype by
itself in its own source member. That means a /COPY for each procedure
used. I don't think that's what was meant in the thread when keeping
prototypes in a separate member was mentioned.

We don't want to pull in all the prototypes from another module, just
those that are actually going to be used. Any constructive criticisme
would be warmly welcomed.



-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
De la part de Bruce Guetzkow
Envoyé : jeudi 20 mars 2008 17:28
À : RPG400-L Posting
Objet : Prototypes in Module Source

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

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.