On Oct 29, 2012, at 23:23 , Quincey Morris <quinceymor...@rivergatesoftware.com> wrote:
> Except that they're not equivalent, in memory management terms. CF and NS > objects have different rules. > > IIRC, it's also not safe to assume that CF and NS (when toll-free bridged for > a class) use the same underlying classes. In some cases they do (often these > are "NSCFxxx" classes at run time), but in a few cases they don't. In yet > other cases (collection classes, for example) it's possible to create CF > objects of a nominally toll-free bridged class which don't work correctly as > NS objects using NS method access (collections that contain non-object > pointers or that use non-standard memory allocators, for example). Well, whatever the __attribute__ is, I'm sure it could specify all that. Then again, I ran into a problem that I don't know how to properly solve, using CFSockets. I need to retain an NSObject I pass into CFSocket, and have it released when the socket is released, not when a callback occurs, but there's no good way to do that. -- Rick _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
