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: G S <email@hidden>
- Date: Sat, 17 Mar 2012 01:45:33 -0700
>
> This pattern is pretty questionable though in terms of OO — you have one
> class (NSNib, UINib, etc.) directly setting instance variables in another
> class (your view controller) and using runtime functions to hack around
> things like @private.
>
How do you figure? I'm not doing any manipulation of non-property members
between classes. If you're saying that Cocoa does it when loading from a
nib, then it's doing that anyway; properties aren't required for that
action. From the end-user (end-programmer) perspective, I don't see any
bad OO going on here.
_______________________________________________
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