Re: Long Constant Names

Kurt,

wwA$ErrUpdStMsg... OK, that looks convincing to me. Well, I don't really like 
the A$, but as you said, it would be used in many places, so it's not that much 
of a problem.

Maybe the real problem is just that I'm not used to this kind of 'shortening' 
technics. So many things to learn, so little time.

Thanks.

--
Antoine CONTAL



                                                                                
                                                       
                                                                                
                                                       
                                                Pour :   "RPG programming on 
the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>              
                                                cc :                            
                                                       
                                                Objet :  RE: Réf. : Re: Long 
Constant Names                                            
             "Kurt Anderson"                                                    
                                                       
             <kjanderson@xxxxxxxxxxxxx>                                         
                                                       
             Envoyé par :                                                       
                                                       
             rpg400-l-bounces@xxxxxxxxxxxx                                      
                                                       
                                                                                
                                                       
                                                                                
                                                       
             29/12/2004 15:02                                                   
                                                       
             Veuillez répondre à RPG                                            
                                                       
             programming on the AS400 /                                         
                                                       
             iSeries                                                            
                                                       
                                                                                
                                                       
                                                                                
                                                       





Antoine,

Freeing up a character here and a character there goes a long way.  Here are 
some suggestions.

>IMHO, each word is important:
>* App: we have both a global batch state and an application state. Updating 
>the global batch state can
>also end in error.

If there are only two states (or even if there are a couple others) and they 
are relatively common (many programs have variables that are named as such), 
the standard could possibly be modified to say "Application State - 'A' (or 
'A$')
prefix" and do something similar with the other states.

>* State: we update both a state for error resuming and some file records.
'St' is a very common abbreviation for State.  Why not use this?

>* Upd: update operations are not the only one that can fail. Another likely 
>error cause is Not Found
>while chaining.
>* Fail: to distinguish success messages and failure messages.
Instead of 'UpdFail' or 'NotFndFail', why not 'Err'?

>* Msg: indicates a message identifier. There is also a wwAppStateUpdFail, 
>which is a procedure return
>code.
I'd keep this one.

>wwAppStateUpdFailMsg could become wwAppSttUpdFlrMsg
What about wwA$ErrUpdStMsg?

Another suggestion, in naming, from left to right go generic to specific.
That way the values will be grouped together in definition (assuming you keep 
them alphabetical).  This allows you to possibly change an abbreviation from 
'Err' to 'Er' and still make it somewhat passable (especially if you group them
together _and_ give the group of field definitions a heading).
There's probably all sorts of styles out there in regard to naming, but I 
honestly can't think of a situation where I couldn't get a field down to 15 in 
length (if not 14, I like a space between the D spec and the actual field name).

Kurt



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.
$!4$!