RE: Procedure Initialization

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

Static kicks butt when you're keeping track of internal statistics, next
available counters, that sort of thing.

It's also very tempting to use it for memory allocations (for example, you
can allocate an array dynamically and keep it local to the procedure,
reallocating it as needed).  The problem is releasing the memory, but that's
an issue for activation group boundaries.  It's the kind of thing that makes
ILE very powerful, but also requires a little more upfront architecture
work.

Joe

> From: Jerry Adams
>
> That's what I figured, Joe, but it's nice to have confirmation.  Plus, I
> never came across the STATIC keyword, but I can see situations where
> that would be useful.  Another bullet in the holster.