× 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.


  1.  Home
  2. RPG400-L
  3. March 2008

RE: Prototypes in Module Source

David:

As Jerry indicated it does not hurt to bring in additional prototypes that
aren't used. In fact most people store all prototypes for a module (or even
an entire service program) in a single source member. Unless there would be
duplicate names for procedures with different tasks (probably not a good
idea) you could put all prototypes for all procedures in an application in a
single source member if you like, although I'd suggest not doing it to that
extreme.

Personally I put all prototypes for a module in a corresponding source
member (RPGLE module AABBBCCCRM has a prototype member named AABBBCCCPR).
Anywhere any procedures from that module are used, this copy book is used.

Hope that clarifies things a bit,
--Bruce Guetzkow




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.