Re: Strategies to prevent class name clashes
Re: Strategies to prevent class name clashes
- Subject: Re: Strategies to prevent class name clashes
- From: Jonathon Mah <email@hidden>
- Date: Sat, 16 Feb 2008 02:41:46 +1030
On 2008-02-16, at 01:43, glenn andreas wrote:
This problem is a C++ problem - not that Objective-C doesn't have
that problem, but it is much rarer (in Objective C you can add
method to a base class without breaking things, which you can't
safely do in C++ since that alters the vtable layout, though adding
ivars can also break things). Objective-C 2.0 also addresses this
problem, but I'm guessing you can't require that.
For completeness, Objective-C 2.0 on the 64 bit runtime avoids the
fragile base class problem, but Objective-C 2.0 on 32 bit is the same
as before.
Jonathon Mah
email@hidden
_______________________________________________
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