Re: Long Constant Names

LOL!  My team writes /free as well, so we don't worry about field name
length.  Nice reason to use /free.

Mike E.


On Tue, 28 Dec 2004 08:40:40 -0500, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> What's extended factor 2?
> 
> Oh, FIXED format!  Forgot about that.
> 
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
> 
> 
> Michael Jacobsen <MJacobsen@xxxxxxxxxxxxxxxx> 
> Sent by: rpg400-l-bounces@xxxxxxxxxxxx
> 12/28/2004 08:29 AM
> Please respond to
> RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
> 
> To
> RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
> cc
> 
> Subject
> Re: Long Constant Names
> 
> Personally, I agree with the convention team.  Having a name that is too
> long is just as hard to read (within the code) as a name that is too
> short.  The problem I have with longer names is that I often will run out
> of space in the extended factor 2 or other specifications where they are
> used.  I think a good meaningful name can be created within the 15 char
> limit.  Your example of wwASUFM is one that is too short.  (7 Chars)
> 
> Mike
> 
> rpg400-l-bounces@xxxxxxxxxxxx wrote on 12/28/2004 05:24:52 AM:
> 
> >
> > Hi group,
> >
> > I'm having an argument with the team that choose our shop's coding
> > style conventions. I'd like to have your opinion on the subject.
> >
> > The heart of the matter lies in this kind of constant declaration:
> >
> > DwwAppStateUpdFailMsg...
> > D                 C                   '...'
> >
> > The convention team says this name is too long. They want everybody
> > to keep their names within the 15-character limit -- indeed, 13
> > meaningful characters after you add the two-character prefix.
> >
> > I think this name is already on the short side. Using so many
> abbreviations won't make newcomers' work any easier.   > Still, isn't it
> more readable than wwASUFM for instance?
> 
> --