On Jan 24, 2014, at 11:12 AM, Kevin Meaney <k...@yvs.eu.com> wrote: > On 24 Jan 2014, at 19:02, David Duncan <david.dun...@apple.com> wrote: > >> Compiler folks could explain this better, but the root issue is that >> __attribute__((NSObject)) doesn’t do as much as you might expect given the >> way you’ve declared it. Its better in the long run to just not rely upon it. > > When you say the way I've declared it, you mean as a readonly property or is > there just a better way to get the desired the result. I don't like the > manual solution I described because it is really declared as an assign then > goes and retains the context. So I'm not finding an answer I'm happy with and > I can't believe others are not having the same problem.
Basically every reference needs to carry the attribute in order for the right thing to be done in all cases. I suspect most people aren’t having this problem because this particular attribute is not very well known or widely used. -- 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
