Re: Static Variables in a subprocedure

[Ken Sims <mdrg7319@xxxxxxxxxxx>]

Hi Barbara and the group -

On Thu, 07 Feb 2008 16:10:17 -0500, Barbara Morris
<bmorris@xxxxxxxxxx> wrote:

> A problem with this technique is that you have to make all the 
> parameters *NOPASS.  There's a way to get around it: Create a second 
> prototype for the procedure with the same EXTPROC, but no parameters; 
> call it something like myproc_reset.  Then when you want the procedure 
> to reset itself, call myproc_reset() instead of myproc(parms).

Personally I define all such "resetable" variables as global
variables.  Most of my service programs have an "open" procedure
(which calls the "reset" procedure), a "reset" procedure, and a
"close" procedure.

I do use some static local variables, but only for purposes where the
caller doesn't have any say about them, or where the procedure
parameters inherently support whatever the caller needs to communicate
about them.

Ken
Opinions expressed are my own and do not necessarily represent the views 
of my employer or anyone in their right mind.