AW: Correct use of STATIC variables

ie, it initializes the variables then returns without performing its

normal task?

It depends.

If I get the optional parameter the static variables will be initialized.
In some routines I check if the other parameters are passed. If so the
procedure will be executed otherwise the procedure will be left.
In other procedures I'll only initialize or execute.
For other procedures I pass my optional parameter with different values,
i.e. only initialize, execute without initialization, execute with
inititalization.

Very often I use global variables instead of static ones and have one or
several procedures to initializes these global variables.
Depending on what I want to achieve, these initialization procedures will be
exported or only internally used.

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, 26. January 2010 15:23
An: RPG programming on the IBM i / System i
Betreff: RE: Correct use of STATIC variables

-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Birgitta Hauser
In this situations I use an optional parameter (simply an
indicator). If this parameter is passed, the static variables
first get initialized.
At the first call, I pass the optional parameter (with *ON)
and for all subsequent the parameter is either not passed or
passed with *OFF.

Hi Birgitta,

Does that mean you have to call all your subprocedures that contain static
variables and include code in each subprocedure so that it behaves
differently, ie, it initializes the variables then returns without
performing its normal task?