|
One might argue that if the CL calls the RPG then perhaps it should be called PGM0010 and the RPG PGM0020, but if the RPG calls the CL then perhaps it should be called PGM0010 and the CL PGM0020. Because, if you are using one source file, such as QPGMSRC, then wouldn't that make more sense then suffixing one with a R and the other with a C? Your editor will pick up the right syntactical checker and compiler based on the member type (or make a reasonable effort for those using modules, etc). One time when I can see adding a suffix on to a program is in the case of trigger programs. I used to name my trigger programs after the file. Well, there are a plethora of reasons to have the trigger program in the same library as the physical file. And the first time you mess up, modify your trigger program on your test machine and do a SAVOBJ/RSTOBJ without specifying *PGM and you clobber your live file with your test file, you learn really fast. Now if you're used to adding suffix's to your files (thinking printer and/or display files), it may be a slight change in paradigm to start adding the suffix on the program (when you're thinking trigger programs and physical files). I suppose you might change the defaults to SAVOBJ to *USRIDX or some rarely used object. But then this might cause some save/restore concerns. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Scott Klement <klemscot@xxxxxxxxxxxx> Sent by: rpg400-l-bounces+rob=dekko.com@xxxxxxxxxxxx 03/27/2003 03:05 PM Please respond to RPG programming on the AS400 / iSeries To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> cc: Fax to: Subject: RE: Naming conventions - was ->RE: Replacing *entry plist The only thing I can think of... *FILE is used for many different object types. Display Files, Print Files, ICF Files, and database files. If your company's convention is to name the display file, print file and ICF file so that it matches the program name (which is the case here) and you don't use some kind of suffix, you end up with a conflict. Likewise, if you have a CL program and an RPG program that work together to accomplish something, you can't name them the same thing unless you use a suffix of some sort, because both compile to a *PGM object. None of this really matters to me, however. You could probably spend days reading the various archives at midrange.com on naming-convention related issues. After reading all of that, still have no clear cut idea of "what is best". The reason is simple: No one way is the best. Each way has pros and cons. Everyone has a different opinion. Just pick a way and be consistent. On Thu, 27 Mar 2003, Bartell, Aaron L. (TC) wrote: > > I keep trying to think of a time where I am looking at an object and don't > have access to the object type. Since iSeries objects can't really be used > anywhere else (to my knowledge) and you always have a way to display the > object type (unless it is third party software you are dealing with) then it > shouldn't be a problem to have a file named the same as a program. > _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
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.