RE: Initialization of static variables

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Bob cozzi
> 
> Joe,
> Why on Earth would you call a module?
> That is the strangest design decision I have seen on this ILE
architecture
> (not your's specifically just in general).
> I mean if you have:
>   CALLP  'MYMODULE'

Um.  Who said I was calling a module, Bob?

Basically, I'm using procedures within a program with a MAIN.  These
procedures perform tasks that require the preservation of data between
calls (static data).  While I can do this using global variables, I'd
rather this data not be visible outside the scope of the procedure, thus
I'd like to use local variables.

So, the obvious choice is to use local static variables with an
initializer.

The problem is that I would like these variables reinitialized each time
the program is called, but they are not (even if the program is bound
with ACTGRP(*NEW)!).  Thus, I have to manually reinitialize the
variables.  And since the data is local to the procedure, I must call
the procedure to initialize the data.  To date, I have done this by
passing no parameters to the procedure.  (This of course only works if
the procedure normally requires parameters.)

I'm not sure where you got "calling a module" from, except maybe by
reading between the lines I quoted of Barbara's explanation.

Joe