Class vs +class: Cocoa/Obj-C design question
Class vs +class: Cocoa/Obj-C design question
- Subject: Class vs +class: Cocoa/Obj-C design question
- From: Chris Ryland <email@hidden>
- Date: Sat, 13 Oct 2007 13:17:53 -0400
Can I ask perhaps a "list in the mists of time" language/library
question? (Or perhaps a dumb question--forgive me if so.)
Why can't a class name (e.g., NSObject) stand for itself in general--
i.e., why isn't NSObject == [NSObject class] the way +class is
defined now?
In theory, NSObject is a class object, and [NSObject class] should be
its metaclass.
Why this breakdown in what otherwise is a very clean language/library
design?
Cheers!
--Chris Ryland / Em Software, Inc. / www.emsoftware.com
_______________________________________________
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