Re: When does manually allocated memory get released?

Hi, Vern:

OAR handlers are certainly a "special case" that should definitely take
care of allocating and freeing their own storage, and not just allocate
a bunch of stuff and "leave it up to the system" to clean it up.
Because, who knows how long a using application (that calls the handler
indirectly , via the F-spec) may be running? It might be a "never ending
program"... :-o

Mark

> On 10/8/2010 12:22 PM, Vern Hamberg wrote:

Mark

I guess I'm of the school that says not to depend on hidden processes to
clean up things. And I'm not sure about using some hidden thing
sometimes, not in other situations.

In the handler I'm working on, I would not want to end the activation
group, since I'm not the one who started it. I'm using *CALLER in the
*SRVPGM that is the handler, as I recall.

I also don't know how many reads or other operations will be done
between open and close. So I want to explicitly dealloc a particular
based DS (that keeps the state between calls) in the event of an error
and when closing the "file".

Just my way today!

Vern