Re: Purpose of [NSAutoreleasePool drain] ?
Re: Purpose of [NSAutoreleasePool drain] ?
- Subject: Re: Purpose of [NSAutoreleasePool drain] ?
- From: Chris Kane <email@hidden>
- Date: Thu, 16 Jun 2005 14:56:44 -0700
On Jun 16, 2005, at 1:59 PM, Finlay Dobbie wrote:
On 6/16/05, Chris Kane <email@hidden> wrote:
But GC isn't here yet (as of Tiger), and who knows if it will ever
happen. We don't expect people to be using -drain today, and I would
advise against it (in case it takes on some new behaviors in the
future).
Please could you explain why this is in the public Tiger headers and
documentation, if that is the case?
Same goes for CFMakeCollectable, which is in the headers but
undocumented.
There's two general reasons: plans change over time, and Apple's
frameworks need to use it today so experiments can continue "in the
lab". It's not always practical to go back later then and move the
declaration and possibly have to update many projects.
One can call it, but I wouldn't until there's a reason to. I didn't
want to give the impression people should go out and change all their
source code. Even under a hypothetical GC environment, thing would
work fine if there was no use of -drain.
Chris Kane
Cocoa Frameworks, Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden