Naming Global Variables -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Naming Global Variables
From: "Kurt Anderson" <kjanderson@xxxxxxxxxxxxx>
Date: Mon, 11 Dec 2006 15:05:28 -0600
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

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?
 
Kurt Anderson
Application Developer
Highsmith Inc.
W5527 State Road 106, P.O. Box 800
Fort Atkinson, WI 53538-0800
TEL (920) 563-9571  FAX (920) 563-7395
EMAIL kjanderson@xxxxxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

AW: Naming Global Variables , BirgittaHauser
Re: Naming Global Variables , James Rich
Re: Naming Global Variables , Steve Richter

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.