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



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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