Re: Core Foundation types as properties
On Mar 28, 2015, at 11:12 PM, dangerwillrobinsondan...@gmail.com wrote: Interesting. So is there a generalized best practice? Generally, to prefer Obj-C objects where possible. There isn’t much that can be done for things without Obj-C equivalents (like CoreGraphics for example). Sent from my iPhone On 2015/03/29, at 14:42, David Duncan david.dun...@apple.com mailto:david.dun...@apple.com wrote: On Mar 28, 2015, at 9:41 PM, dangerwillrobinsondan...@gmail.com mailto:dangerwillrobinsondan...@gmail.com wrote: See this http://stackoverflow.com/questions/9274397/retained-core-foundation-property http://stackoverflow.com/questions/9274397/retained-core-foundation-property __attribute__((NSObject)) is not recommended, as it doesn’t necessarily cause the behavior you want in all cases. Basically the attribute can get disassociated from the underlying type, and thus “lose” the NSObject-ness, causing the handling you desire to be lost. Sent from my iPhone On 2015/03/29, at 12:16, Graham Cox graham@bigpond.com mailto:graham@bigpond.com wrote: Just a general question: What do people do about properties that are CF type objects (both ARC and non-ARC)? Typically I want these retained, but that doesn't work, at least in non-ARC code, because CF types aren't recognised as being retainable. So I declare them as 'assign' but usually leave a comment that it's really copied, CFRetain'd, etc. (and of course I have to write the setter methods myself to make that true). Is that my only option? It would be nice if this were better supported. --Graham ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com mailto: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 http://lists.apple.com/ Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com This email sent to dangerwillrobinsondan...@gmail.com mailto:dangerwillrobinsondan...@gmail.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com mailto: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 http://lists.apple.com/ Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/david.duncan%40apple.com https://lists.apple.com/mailman/options/cocoa-dev/david.duncan%40apple.com This email sent to david.dun...@apple.com mailto:david.dun...@apple.com -- David Duncan -- David Duncan ___ 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
Re: Core Foundation types as properties
Interesting. So is there a generalized best practice? Sent from my iPhone On 2015/03/29, at 14:42, David Duncan david.dun...@apple.com wrote: On Mar 28, 2015, at 9:41 PM, dangerwillrobinsondan...@gmail.com wrote: See this http://stackoverflow.com/questions/9274397/retained-core-foundation-property __attribute__((NSObject)) is not recommended, as it doesn’t necessarily cause the behavior you want in all cases. Basically the attribute can get disassociated from the underlying type, and thus “lose” the NSObject-ness, causing the handling you desire to be lost. Sent from my iPhone On 2015/03/29, at 12:16, Graham Cox graham@bigpond.com wrote: Just a general question: What do people do about properties that are CF type objects (both ARC and non-ARC)? Typically I want these retained, but that doesn't work, at least in non-ARC code, because CF types aren't recognised as being retainable. So I declare them as 'assign' but usually leave a comment that it's really copied, CFRetain'd, etc. (and of course I have to write the setter methods myself to make that true). Is that my only option? It would be nice if this were better supported. --Graham ___ 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/dangerwillrobinsondanger%40gmail.com This email sent to dangerwillrobinsondan...@gmail.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: https://lists.apple.com/mailman/options/cocoa-dev/david.duncan%40apple.com This email sent to david.dun...@apple.com -- David Duncan ___ 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
Re: Core Foundation types as properties
See this http://stackoverflow.com/questions/9274397/retained-core-foundation-property Sent from my iPhone On 2015/03/29, at 12:16, Graham Cox graham@bigpond.com wrote: Just a general question: What do people do about properties that are CF type objects (both ARC and non-ARC)? Typically I want these retained, but that doesn't work, at least in non-ARC code, because CF types aren't recognised as being retainable. So I declare them as 'assign' but usually leave a comment that it's really copied, CFRetain'd, etc. (and of course I have to write the setter methods myself to make that true). Is that my only option? It would be nice if this were better supported. --Graham ___ 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/dangerwillrobinsondanger%40gmail.com This email sent to dangerwillrobinsondan...@gmail.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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Core Foundation types as properties
On Mar 28, 2015, at 9:41 PM, dangerwillrobinsondan...@gmail.com wrote: See this http://stackoverflow.com/questions/9274397/retained-core-foundation-property http://stackoverflow.com/questions/9274397/retained-core-foundation-property __attribute__((NSObject)) is not recommended, as it doesn’t necessarily cause the behavior you want in all cases. Basically the attribute can get disassociated from the underlying type, and thus “lose” the NSObject-ness, causing the handling you desire to be lost. Sent from my iPhone On 2015/03/29, at 12:16, Graham Cox graham@bigpond.com mailto:graham@bigpond.com wrote: Just a general question: What do people do about properties that are CF type objects (both ARC and non-ARC)? Typically I want these retained, but that doesn't work, at least in non-ARC code, because CF types aren't recognised as being retainable. So I declare them as 'assign' but usually leave a comment that it's really copied, CFRetain'd, etc. (and of course I have to write the setter methods myself to make that true). Is that my only option? It would be nice if this were better supported. --Graham ___ 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/dangerwillrobinsondanger%40gmail.com https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com This email sent to dangerwillrobinsondan...@gmail.com mailto:dangerwillrobinsondan...@gmail.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com mailto: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 http://lists.apple.com/ Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/david.duncan%40apple.com https://lists.apple.com/mailman/options/cocoa-dev/david.duncan%40apple.com This email sent to david.dun...@apple.com mailto:david.dun...@apple.com -- David Duncan ___ 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
