Re: In-loop releasing of objects does not free memory?

FROM : Michael Watson
DATE : Thu Feb 14 22:00:53 2008

Nick is referring to this bit from the -drain documentation:

"In a garbage collected environment, triggers garbage collection if 
memory allocated since last collection is greater than the current 
threshold; otherwise behaves as release."

When you aren't using GC, calling -drain on your AutoreleasePool 
object will act just like you called -release on it. As a result, in a 
loop construct like that, you'll crash if you aren't using GC.


--
m-s

On 14 Feb, 2008, at 15:54, Randall Meadows wrote:

>> That'll cause a crash if GC isn't being used, since -drain is 
>> documented as doing the same thing as -release in non-GC 
>> applications.

>
> I took that to mean that has the same effect on the *contents* of 
> the pool (that is, releasing everything contained in the pool) but 
> doesn't release the pool itself.  Am I being too liberal in my 
> interpretation, or are you talking about something else?
> _____________