Re: Long Constant Names

Antoine,

Personally I'm not sure why you need context in the variable name.  Context
should be provided by where the constant is defined.  Don't define the
constant in a global list but define it in the procedure where it is used.
If that requires multiple definitions of the constant in multiple procedures
then accept that or put
the constant definition in a /copy book.  If it's in a /copy book then the
name of the copied member would also provide the context (/Copy AppState).
wwUpdateFailMsg won't work as a variable name if it's defined 'close' to
where it is used?

I'd also try to take Msg out of the constant name.  That's really a 'type'
suffix you've added on to the name.  Lowercase m might suffice as either a
prefix (polish) or a suffix.  wwmUpdateFailure won't work as a variable
name?

Paul

-- 
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333
<antoine.contal@xxxxxxx> wrote in message
news:OFB9E16CC5.1EDAD2F2-ONC1256F7A.00584DA7-C1256F7A.0059201B@xxxxxxxxxx
>
>
>
>
> Steve,
>
> You're right. In fact, this double semantic load a constant has to bear is
the reason I'm talking about constant names specifically, and not variable
names in general. Generally speaking, the constant should state both the
context (e.g.,
> 'dayofweek', 'ErrMsg') and the value (e.g. 'monday', 'StUpd').
>
> I'd rather put an underscore between the two parts, but if I can't have
more than 15 chars, I have to use chars sparingly.
>
> Regards.
>
> --
> Antoine CONTAL
>
>
>
> something else to keep in mind is that a constant will 99% of the time
> be one of a set of values.
>    dayofweek_monday
>   dayofweek_tuesday
>
>   statuscode_active
>   statuscode_held
>   statuscode_deleted
>
> It follows that the constant name should always indicate that
> relationship. What better way is there than the first half of the name
> is the name of the constant set, the second half is the name of the
> constant within that set? You dont have to use the underscore if you
> dont want to.
>
> -Steve
>
>
>
> Les informations contenues dans ce message sont confidentielles et peuvent
constituer des informations privilegiees. Si vous n etes pas le destinataire
de ce message, il vous est interdit de le copier, de le faire suivre, de le
divulguer ou d en utiliser tout ou partie. Si vous avez recu ce message par
erreur, merci de le supprimer de votre systeme, ainsi que toutes ses copies,
et d en avertir immediatement l expediteur par message de retour.
> Il est impossible de garantir que les communications par messagerie
electronique arrivent en temps utile, sont securisees ou denuees de toute
erreur ou virus. En consequence, l expediteur n accepte aucune
responsabilite du fait des erreurs ou omissions qui pourraient en resulter.
> --- ----------------------------------------------------- ---
> The information contained in this e-mail is confidential. It may also be
legally privileged. If you are not the addressee you may not copy, forward,
disclose or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the sender
immediately by return e-mail.
> E-mail communications cannot be guaranteed to be timely secure, error or
virus-free. The sender does not accept liability for any errors or omissions
which arise as a result.
> $!1$!
>
> -- 
> 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.
>
>