on 2008-07-06 10:50 AM, Clark Cox at [EMAIL PROTECTED] wrote: >> He even goes so far as to suggest that it would be >> dangerous or at least inefficient to use __strong in a mixed environment >> such as a shared framework that supports both garbage collection and >> retain/release, due in part to the additional overhead. > > What "additional overhead" does he imagine will be incurred?
CFMakeCollectable as a no-op in a retain/release environment? Which I'm not sure makes sense. But I am becoming persuaded that your Option #2 is in fact the way to go. (Even though I can avoid the collection time overhead of -finalize by implementing some sort of wrapup system such as I outlined in another message.) -- Bill Cheeseman - [EMAIL PROTECTED] Quechee Software, Quechee, Vermont, USA www.quecheesoftware.com PreFab Software - www.prefabsoftware.com _______________________________________________ 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]
