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



Scott Klement wrote:
QMODSRC for a module? That's a little different from what I was expecting. You name your source files based on the output object type instead of the language they're written in... Hmmm... never thought of that.

I know a lot of folks use QDDSSRC for stuff written in DDS, QRPGSRC for RPG, QRPGLESRC for RPGLE, QCLSRC for CL, etc. So it's based on the language the code is written in.

But you say QMODSRC for a module... you can write modules in many languages, ILE RPG, ILE CL, ILE C, ILE COBOL, ILE C++... presumably they all share the same QMODSRC file? Interesting...


Bruce Guetzkow wrote:
I appreciate your comments. Rather than use a single source file for
all I use source files based on the object type being created
(QDDSSRC - *FILE, QMODSRC - *MODULE, etc.). Since the prototypes
aren't objects, I keep them in a separate source file. I could have
kept them in QMODSRC, just chose to do it differently. QCPYSRC also
has members with D-specs for named constants that I copy into
multiple sources, API data structures (SPLA0100, etc.). Just my way
of thinking.

I use this technique for modules vs. programs, too. I do it because my CRTOBJ command can then determine different default behaviors based on whether compiling a module or a program. It works quite well, actually.

Joe

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.