Re: Why so many public properties all up in my grizzle?
Re: Why so many public properties all up in my grizzle?
- Subject: Re: Why so many public properties all up in my grizzle?
- From: "T.J. Usiyan" <email@hidden>
- Date: Thu, 22 Mar 2012 20:43:26 -0400
Well damn, @package accomplishes the 'compilation unit' request.
On Thu, Mar 22, 2012 at 8:36 PM, T.J. Usiyan <email@hidden> wrote:
>
>> > 2) Technically, nothing is truly private in Objective-C, so let's stop
>> > trying to completely prevent people from using private APIs.
>>
>>
>> contradiction++
>> _______________________________________________
>>
>>
> Not quite. You actually CAN hide the ivars and it is odd to expose them
> because you have the ability to hide them. Exposing the accessor method
> INSTEAD of the ivar is usually better. I know that it is not always
> convenient and hope that we eventually get the ability to access self's
> ivars if we are in the same compilation unit, but until then, exposing
> accessors seems like a better option.
>
> TJ
>
_______________________________________________
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