On Jun 28, 2009, at 16:12, Michael Ash wrote:
Your way sounds sensible, but according to the docs that's not how
it is.
We'll have to wait for b.bum to adjudicate, since the docs contradict
what he said earlier:
On Sat, Jun 27, 2009 at 9:47 PM, Bill Bumgarner<b...@mac.com> wrote:
When a CF object is created, it is CFRetain()ed and, thus, the
collector
will ignore it. If it is then managed entirely through a balanced
set of
CFRelease() and CFRetain() calls, it'll work just like it does under
non-GC.
If you call CFMakeCollectable(), that'll effectively balance the
CFRetain()
at creation while making the collector aware of the object.
His "just like it does" strongly implies that the memory is disposed
of immediately, unless he meant "just like it does under non-GC,
except for the timing of disposal".
His "making the collector aware of the object" contradicts the docs,
since that would be a third thing CFMakeCollectable does.
Of course, it might work the way the docs say in Leopard, and possibly
Bill was talking about possible future behavior in some possible
future Mac OS X.
_______________________________________________
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 arch...@mail-archive.com
