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

I know it is really a personal preference, but give me one really solid
reason why you shouldn't combine source members this way?  For me, doing
so is a productivity benefit!  What were the reasons your shop gave you?

I was at a seminar in 96 given by Charlie Massoglia who ranted and raved
about this very subject for upwards of 10 minutes - and of course his
argument was that it gained productivity having one source file.  So I
know I am not alone in my view.

Of course, with Code Project Organizer (CPO), this is somewhat a moot
point; although you still gain some benefit by not having to search all
the different source files as you add members to your project.  (Haven't
looked at iSeries projects in WDSc yet)

Why does that make me a heretic?  Is my view a "pc-world" bias?  I
wouldn't know as I've only been on the 400 my whole career :)

Bob Cagle
IT Manager
Lynk, Inc.
8241 Melrose Drive
Lenexa, KS  66214
913-492-9202 ext.41
mailto:bcagle@xxxxxxxxxxx


-----Original Message-----
From: Booth Martin [mailto:Booth@xxxxxxxxxxxx] 
Sent: Wednesday, March 26, 2003 3:03 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Naming conventions - was ->RE: Replacing *entry plist

You are a Heretic!  The firey cross for you.



I tried that, with the sourcefiles by application, i.e., AP = Accounts
payable.



Boy did I get shot down. 

 

---------------------------------------------------------

Booth Martin   http://www.MartinVT.com

Booth@xxxxxxxxxxxx

---------------------------------------------------------

 

-------Original Message-------

 

From: RPG programming on the AS400 / iSeries

Date: Wednesday, March 26, 2003 15:50:14

To: RPG programming on the AS400 / iSeries

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

 

I have always utilized a suffix on CL & DDS as I only use one source

file. When looking at the source files with PDM (and now RSE), this

alphabetically sorts all like source members together so I don't have to

go jumping around different source files just to work on one process.



Bob Cagle

IT Manager

Lynk, Inc.

8241 Melrose Drive

Lenexa, KS 66214

913-492-9202 ext.41

mailto:bcagle@xxxxxxxxxxx





-----Original Message-----

From: Bartell, Aaron L. (TC) [mailto:ALBartell@xxxxxxxxxxxxxx] 

Sent: Wednesday, March 26, 2003 2:11 PM

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



-----Original Message-----

From: Joel Fritz [mailto:JFritz@xxxxxxxxxxxxxxxx]

Sent: Wednesday, March 26, 2003 1:41 PM

To: 'RPG programming on the AS400 / iSeries'

Subject: RE: Replacing *entry plist





I like ending both physical and printer file names with "P." I'd add a

smiley, but I've seen it a lot. 



_______________________________________________

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.



.