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



Because you cannot have two objects
of type *PGM in the same library
with the same name, even if the
attribute is different.  That is,
you cannot have a MYPROG
that was written in CL and a
MYPROG that was written in
RPG.  Nor can you have multiple
members with the same name
in the same source file, so if
you organize your sources by
application (APSOURCE contains
all the AP source code, etc) you
have to have an naming convention
that will avoid conflict.

If you use QCLSRC, QDDSSRC, QRPGSRC, etc.
then you have my sympathy.  I've had
to deal with that, too and it is no fun in
PDM.  Not to bad with RSE.

Lance


date: Wed, 22 Feb 2006 17:21:41 -0500
from: rob@xxxxxxxxx 
subject: Re: Naming Conventions on Your Programs

Why do you have the YY?  Do all of your PC files have names like
myfiletxt.txt
myfilexls.xls
myfiledoc.doc
No.  They why do some insist on it in a program name?  What happens if

your program is composed of modules of different languages?  Does it
then 
become
MYPGMCLRPGCPP?



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.