Re: @property problem
Re: @property problem
- Subject: Re: @property problem
- From: Bill Bumgarner <email@hidden>
- Date: Sun, 17 Feb 2008 12:09:53 -0800
On Feb 17, 2008, at 10:52 AM, William Squires wrote:
Okay, that explains it - weird... I wonder why ObjC did that?
When Objective-C was created, the targeted machines had relatively
little memory -- 4MB or less, typically.
As such, every single byte that could be saved was valuable. So, as
a simple extension of C, Objective-C classes are really just a
glorified C structure that is extended across subclasses and has a
slot at the head that can point to the class of the structure.
Simple. Elegant. Compact. Easy to implement. And prone to the
fragile base class problem.
While memory is still at a premium, eating a couple of pointers worth
of memory to solve the fragile base class problem is now a worthwhile
tradeoff.
It would have been nice if this change could have been made in the
10.0 timeframe when there wasn't a binary compatibility issue
preventing adoption in 32 bits. But, at the time, there were other
priorities that out weighed solving this particular problem.
b.bum
_______________________________________________
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