RE: Initialisation of global variables between calls

Why use global variables at all? If you need to keep data between calls you can use the static keyword in most cases.

Mihael

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Birgitta Hauser
Sent: Tuesday, November 16, 2010 12:16 PM
To: 'RPG programming on the IBM i / System i'
Subject: AW: Initialisation of global variables between calls

Why not simply adding an internal procedure where all global variables get
initialized (or reset)?
This procedure can be called by the main procedure (like any other
procedure).

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von David FOXWELL
Gesendet: Tuesday, 16. November 2010 11:21
An: RPG programming on the IBM i / System i
Betreff: Initialisation of global variables between calls

Hi,

Just wondering what is a good/normal approach to this. Starting to use
linear main programs has made me stop and rethink.

Say I have a program that treats a client, ends, then treats another client.

Up until now, I've just relied on the program analysis to set the variables
at the right place. So at any given time, there could be global variables
containing information on the current client and others still containing
information on the previous client until they are used.

In a linear main program, wouldn't it be easiest to just initialise all
global variables in the main procedure? Would it work if they were all
declared as part of a data structure so that they could be reset by one
command?

I know, reducing the number of global variables would also help.