Re: Naming Global Variables

My standard is to use g_ for all global variables to avoid any problem
with the same name variable ending up in global and local storage so
g_OpenList. 

I use c in front to indicate a constant so cHomeDirectory. 

I use Upper Case for anything that comes from a database, file name,
file name, record format. Normally a constant would be all upper case
but it extremely important to me to know that a field is coming from a
database table SQL or File I/O. 

Anything else is mixed case. 

For local variables, I am still moving back and forth between having no
prefix and using w_ for work variables. Just can't decide which way to
go on that. As long as I am religious about putting a g_ on the front of
any global variable, it shouldn't matter.

I, also, name any data structures declared as a type definition (Based
on a pointer only used to define another structure or variable) as TD_
so I know they are type definitions. 

I am waiting and waiting for IBM to give us type definitions in RPG. It
will make life so much easier.