Re: When does manually allocated memory get released?

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

 Y'all

I'm working with %alloc'd space, too, in an Open Access-RPG handler. If 
you want to keep state for an opened file, you pass a pointer back to 
RPG engine for that file - RPG keeps track of it for you and gives it 
back to you on the next op-code.

I'm making sure to %dealloc it when there's an error - otherwise this 
could be a gaping memory leak! Methinks!

These handlers need to run as *CALLER for AG, too, for all the reasons 
discussed in that other thread on triggers. Meaning that I'm not 
controlling any of the job end or AG end.

Interesting stuff!
Vern

On 10/7/2010 3:02 PM, Bryce Martin wrote:
> List Experts...
> I'm currently using a pointer based array and manually
> allocating/reallocating space for the array.  This program runs in a named
> activation group.   If I don't manually deallocate (maybe due to an
> uncaught error), does the memory get release when the AG is destroyed or
> when the job ends?  I'm guessing its when the AG is destroyed, but I'd
> like to make sure.
>
>
> Thanks
> Bryce Martin
> Programmer/Analyst I
> 570-546-4777
> --- This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us and destroy this message immediately. ---