RE: Externalizing I/O was RPG read loops

["Joel Fritz" <JFritz@xxxxxxxxxxxxxxxx>]

I once worked with a guy who used his own flavor of Hungarian notation
in his variable names.  Unfortunately, he also preferred six character
names. Sometimes he went as far as eight. When the suffix was more than
one character long things got pretty interesting.  Once when he was
drafted to help another programmer finish a project they had a
protracted argument on the use of prefixes for field names in files and
externally described data structures.  He was against them because he
didn't like the way they were grouped in the compile listing.  He
preferred to code an externally defined data structure by specifying the
name and from/to for each field using the "ds" suffix.

    

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Wednesday, February 02, 2005 1:45 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Externalizing I/O was RPG read loops

> From: Paul Morgan
>
> Can't do a one character typo unless the procedure names are very
> abbreviated.

Now THIS is a very powerful comment.  I don't think I ever thought of it
quite that way.  An extension of this is that you should try to make
sure that your field names are not just meaningful, but also as
different as is practical.  Don't go overboard, certainly, but this is a
good argument against names like "Field1" and "Field2" <grin>.

Joe

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


*****************************
NOTICE:
All e-mail sent to or from this e-mail address will be received or otherwise 
recorded by
The Sharper Image corporate e-mail system and is subject to archival, 
monitoring,
and review by and/or disclosure to Sharper Image security and other management.
This message is intended only for the use of the addressee and may contain 
information
that is privileged and confidential.

The contents of this message may contain personal views which are not the views 
of The Sharper Image.
If you are not the intended recipient, dissemination of this communication is 
prohibited.
*****************************