On 7/4/08, Chris Hanson <[EMAIL PROTECTED]> wrote: > Under non-GC, an object's memory may not be reclaimed until the current > autorelease pool is drained. However, under GC, an object's memory can be > reclaimed as soon as the collector can tell there are no more references to > it -- no matter when that is.
I think Joan's point is not that there are circumstances in which the GC will never reclaim, but that it is not possible to ensure reclamation deterministically. >From the docs: -------- collectExhaustively Tells the receiver to collect iteratively. - (void)collectExhaustively Discussion You use this method to indicate to the collector that it should perform an exhaustive collection. Collection is subject to interruption on user input. Availability Available in Mac OS X v10.5 and later. Declared In NSGarbageCollector.h -------- "Collection is subject to interruption on user input" -- with no mention of when it might be re-started. Hamish _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
