Re: Procedure Initialization

I have found STATIC useful in a routine that calls QWCRSYSVAL API to get the
system's date format (QDATFMT). The date format goes to a STATIC variable,
and the API only gets called if the static variable is blank. Therefore, the
API only gets called once per job (the first time it's needed), no matter
how many date calculations the service program is doing. I hate needless
repetition.

On 8/21/07, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:

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.

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.