Le 30 juil. 2013 à 17:25, Scott Ribe <scott_r...@elevated-dev.com> a écrit :
> On Jul 30, 2013, at 9:08 AM, Andy Lee <ag...@mac.com> wrote: > >> I think it's subject to the same criticisms as *any* direct access to ivars, >> although I agree it feels sketchier when done in plain C for some reason. > > Yes. Because what is the point of plain C functions in Objective-C files? > Local helpers that are not OOP, and do not go through method dispatch > overhead. To turn around and inject direct access to ivars in those is really > mixing metaphors. > >> Which reminds me... instance methods can also directly access the ivars of >> *other* instances of the same class. > > Now, *that* I knew. I'm sorry senator, I cannot recall if I ever did such a > thing. But I knew it was possible ;-) I think I don't have a single copyWithZone: implementation that does not use this feature. Foo *copy = [super copyWithZone:]; copy->_myivar = _myivar; Especially as all ivars are not exposed as properties. -- Jean-Daniel _______________________________________________ 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
