🚀 go-pugleaf

In article <1992Apr14.232745.12859@crd.ge.com>, hoffman@albirio.NoSubdomain.NoDomain (William A. Hoffman) writes:
|> 	I am using the 2.6 compatibility mode in iv 3.01.  Several of my classes
|> inherit from Subject which inherits from Resource.  My program had a large
|> memory leak because of the following:
|>  ...
|> All my code is going to be executed from the e.handle() call.  In effect this
|> means that Resource::defer is defaulted to true not false as it is stated in
|> the manual.   
|> 
|> 	Is this a bug or a feature?  Should I wrap all my code that is called
|> from handle functions with:
|> 
|> 	b = Resource::defer(false); my code;  Resource::defer(b);  

This is a feature.  It is common during the process of event handling
to want to "free" an object with an active method on the stack.
So we defer all destruction until after each event is handled.
If you want memory to be freed during the execution of your event handler,
then you do need to turn off deferral.