Re: Understanding the "declaration of instance variables in the interface is deprecated" warning.
Re: Understanding the "declaration of instance variables in the interface is deprecated" warning.
- Subject: Re: Understanding the "declaration of instance variables in the interface is deprecated" warning.
- From: Britt Durbrow <email@hidden>
- Date: Thu, 04 Jun 2015 11:13:41 -0700
> On Jun 4, 2015, at 9:16 AM, Uli Kusterer <email@hidden> wrote:
>
>
>> On 04 Jun 2015, at 02:36, Britt Durbrow <email@hidden> wrote:
>>
>>
>>> On Jun 3, 2015, at 11:30 AM, Mark Wright <email@hidden> wrote:
>>>
>>> For what it’s worth, I’ve never had that problem either. Most of the time self.whatever is used for property access, _whatever is used for ivar access and that’s about it.
>>
>> Yup. This is what I meant about properties vs ivars being obvious from context: the only way to do a property access is by causing a message send; and there are only three direct ways to do that in Objective-C: somePointer.accessor (i.e, dot notation); [somePointer accessor] and [somePointer setAccessor:aNewValueGoesHere]; and a direct call to objc_msgSend().
>
> There’s also key-value coding, i.e. [obj valueForKey: @“accessor”] and [obj setValue: @1 forKey: @“accessor”], and the implicit occurrences thereof in e.g. XIB loading.
>
I would classify that as an indirect way, as it’s not actually built into the language (it comes from NSObject)… and FWIW, there’s also NSInvocation, and any number of third-party invocation or KVC wrappers.
_______________________________________________
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