• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Core Foundation types as properties
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Foundation types as properties


  • Subject: Re: Core Foundation types as properties
  • From: David Duncan <email@hidden>
  • Date: Mon, 30 Mar 2015 00:26:35 -0700

> On Mar 28, 2015, at 11:12 PM, email@hidden 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 <email@hidden <mailto:email@hidden>> wrote:
>
>>
>>> On Mar 28, 2015, at 9:41 PM, email@hidden <mailto:email@hidden> 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 <email@hidden <mailto:email@hidden>> 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 (email@hidden <mailto:email@hidden>)
>>>>
>>>> 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:
>>>>
>>>> This email sent to email@hidden <mailto:email@hidden>
>>> _______________________________________________
>>>
>>> Cocoa-dev mailing list (email@hidden <mailto:email@hidden>)
>>>
>>> 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:
>>>
>>> This email sent to email@hidden <mailto:email@hidden>
>> --
>> David Duncan
>>

--
David Duncan

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


References: 
 >Core Foundation types as properties (From: Graham Cox <email@hidden>)
 >Re: Core Foundation types as properties (From: email@hidden)
 >Re: Core Foundation types as properties (From: David Duncan <email@hidden>)
 >Re: Core Foundation types as properties (From: email@hidden)

  • Prev by Date: NSOpenPanel accessoryView clicks must hit pixels to work
  • Next by Date: Re: NSOpenPanel accessoryView clicks must hit pixels to work
  • Previous by thread: Re: Core Foundation types as properties
  • Next by thread: AVCaptureView not showing any preview video
  • Index(es):
    • Date
    • Thread