On Oct 11, 2009, at 7:46 PM, Ben Haller wrote:
Besides that, I just needed to change a few retains and releases around, because I was mixing CF calls and Cocoa calls in an inconsistent way in a few places. And that was it; as far as I can tell, it now runs nicely on all the target platforms. I almost decided that I needed to use an NSPointerArray for something in the GC-supported case, in which case perhaps I would have had to #ifdef; but it turned out that a mutable CFArray with null callbacks was sufficient.
Be careful. Any CF container with null callbacks is extremely dangerous in GC. It's easy to create a situation where the container or a reader of the container gets a pointer to an object that the GC has thrown away.
-- Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ 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
