On 26/05/2010, at 10:13 PM, vincent habchi wrote: > If I am not mistaken, if your superclass ivar is private (!= protected), it > cannot be accessed from its subclasses. Thus, the compiler can choose to > reuse part of the heap dedicated to private variables to implement subclasses > own private ivars.
I'm pretty sure you are mistaken. If this were even remotely true, object programming would be impossible. @private only declares the visibility of an ivar to its subclasses, it does not give the compiler carte blanche to write over anything it fancies. --Graham _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
