× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



David,

Pulling in unused prototypes (method 2) does not create a strain on the program. It does make the compilation listing longer, but that's about it. I use RPG xTools, and it copies in all of the prototypes for its modules even if I only use one or two.

* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



David FOXWELL wrote:
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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.