Re: Autorelease Question
Re: Autorelease Question
- Subject: Re: Autorelease Question
- From: Jean-Daniel Dupas <email@hidden>
- Date: Thu, 20 Nov 2008 09:53:22 +0100
Le 20 nov. 08 à 05:48, Kyle Sluder a écrit :
On Wed, Nov 19, 2008 at 11:38 PM, Michael Ash
<email@hidden> wrote:
Seriously, this kind of hysteria does nobody any good. Nothing you do
besides explicitly releasing/draining an NSAutoreleasePool instance
that you explicitly created is going to drain the current autorelease
pool. You cannot make a call that "hits the top of the runloop", as a
call is going deeper into the stack by definition, and the top of the
runloop is shallower in the stack. If they run a nested runloop then
fine, those things nest.
There's a reason that the documentation says "normally guaranteed,"
not just "guaranteed":
"A received object is normally guaranteed to remain valid within the
method it was received in (exceptions include multithreaded
applications and some Distributed Objects situations, although you
must also take care if you modify the object from which you received
the object)."
Yes, that's because there is some exception:
"(exceptions include multithreaded
applications and some Distributed Objects situations, although you
must also take care if you modify the object from which you received
the object)."
_______________________________________________
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