RE: Naming Global Variables

Thanks for everyone's input.

Right now when I have a constant I try to either make it all caps and
use an underscore between words, or I do something like LBL_OrderNum
(which could contain a screen label).  The idea of prefixing with a
lower case c is appealing to me.  Possibly the g as well for globals.

I know the use of global variables should be limited, and normally they
are.  If it's a good day my only globals are logic control of the main
(which could arguably have no logic control) and RRNs.

Thanks again,

Kurt Anderson
Application Developer
Highsmith Inc

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
Sent: Monday, December 11, 2006 4:32 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Naming Global Variables

On 12/11/06, Kurt Anderson <kjanderson@xxxxxxxxxxxxx> wrote:

I know when it comes to Naming everyone has their own method, good or 
bad.  But I was curious if anyone had any standards for naming their 
global variables.  I prefix mine with G@ which I don't particularly 
like sometimes, but I do want the variable name to be noticeably 
different when someone is in a procedure so they know the variable is 
global.  One common example of when I do this is for an RRN field.

Also, for those of you who do prefix global variables, do you use that

prefix when the variable is only ever used in an entry module's 
mainline code?

prefix with a lowercase "g".  I would challenge the use of 99% of
globals however. parms and control block type structs passed by ref are
better. Other than RRN and *IN what else does RPG force to be used
globally? ( just because RPG allows pgm main variables to be used
globally doesnt mean you should use them that way! )

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