Re: In-loop releasing of objects does not free memory?
Re: In-loop releasing of objects does not free memory?
- Subject: Re: In-loop releasing of objects does not free memory?
- From: John Stiles <email@hidden>
- Date: Thu, 14 Feb 2008 13:39:30 -0800
Isn't it too late, though? If even one shipped program relies on the old
behavior, it's carved in stone.
Keith Duncan wrote:
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.
I've filed a bug on this and would encourage everyone to do the same.
In my opinion -drain should do as the name implies; call -release on
all the objects currently autorelease'd but not release the pool itself.
Keith
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden