Re: Static Variables in a subprocedure

Kurt Anderson wrote:

Every so often I come across a situation where I'd like to use a static variable in a subprocedure because I want to keep that variable's value between subP calls - and if I can keep it encapsulated and not have to make it a global variable, all the better. But the one thing I can never really get a grip on is how to control when I should be resetting that value. A typical use for this may be a subprocedure that toggles a value on the screen. So if I could call toggleValue() the subP would already know the current toggle state.
Should I add a *nopass parm that is used to tell the subP that I want the toggle value reset? I'm just curious how the general community is doing this. I'm currently using a global variable to control this (or if not global a higher level local variable).

You've hit on the right answer, I think, Kurt. You've got one of two choices, basically. If you're already passing an opcode parameter (something to tell the subprocedure what to do) then adding an "INIT" opcode is the best way. But if you're not, then changing the number of parms is as good a way to communicate as any. If you normally DO pass parameters, then DON'T pass any to signal a initialization. If you normally DON'T pass any parameters, then DO pass one to signal initialization.

Joe