RE: Naming conventions - was ->RE: Replacing *entry plist

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.

Aaron Bartell

-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Thursday, March 27, 2003 12:36 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Naming conventions - was ->RE: Replacing *entry plist


And what possible disaster would that be?  You can have a file and a 
program of the same name.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Booth Martin" <Booth@xxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/27/2003 11:08 AM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     <rpg400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: Naming conventions  -  was ->RE: Replacing 
*entry plist


 In that scenario you then need to worry about "noun & verb." 

When someone names their  *FILEs "APNAMES", "APNAMES1", "APNAMES2" and 
names
their *PGMs "APNAMES", "APNAMES1", "APNAMES2" you have a recipe for 
disaster
  One source file named QAPSRC   prevents those kinds of names collision.
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: Thursday, March 27, 2003 09:09:36
To: RPG programming on the AS400 / iSeries
Subject: Re: Naming conventions - was ->RE: Replacing *entry plist
 
Actually Booth, if by "compiled objects" you mean programs and files, no, 
they do not need a unique name. The iSeries differentiates by object 
type. Or you can think of it in PC terms WRKLNK 
'/QSYS.LIB/MYLIB.LIB/MYOBJ.*' may result in MYOBJ.PGM, MYOBJ.FILE, 
MYOBJ.DTAARA, etc.
 
If by "compiled objects" you mean the RPGLE and the CL program you are 
right. But then that is all the more reason for keeping program source in 
one source physical file, to avoid name collisions.
 
Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 
 
 
 
 
"Booth Martin" <Booth@xxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/26/2003 03:47 PM
Please respond to RPG programming on the AS400 / iSeries
 
To: <rpg400-l@xxxxxxxxxxxx>
cc: 
Fax to: 
Subject: Re: Naming conventions - was ->RE: Replacing 
*entry plist
 
 
careful! The compiled objects need unique names, too.
 
 
 
 
 
 
 
---------------------------------------------------------
 
Booth Martin http://www.MartinVT.com
 
Booth@xxxxxxxxxxxx
 
---------------------------------------------------------
 
 
 
-------Original Message-------
 
 
 
From: RPG programming on the AS400 / iSeries
 
Date: Wednesday, March 26, 2003 15:38:42
 
To: 'RPG programming on the AS400 / iSeries'
 
Subject: Naming conventions - was ->RE: Replacing *entry plist
 
 
 
I have thought about the names of my source members and objects a lot in 
the
 
past couple of weeks, and being that there is such a huge limitation on 
the
 
amount of chars you can use to name something I am wondering why we even 
use
 
a suffix when we have the object type to do that for us??
 
 
 
Of course you would have to put your source in different source members 
like
 
QDDSSRC, QDSPSRC, QMODSRC, QSRVSRC, QPNLSRC, QRPGLESRC, etc so they 
wouldn't
 
collide in the source physical file.
 
 
 
I wonder if that limitation (max of 10 characters for names) is ever going
 
to get better??
 
 
 
Aaron Bartell_______________________________________________
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.
 
 
_______________________________________________
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.
 
. 

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


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