Re: Mutable class problems
Re: Mutable class problems
- Subject: Re: Mutable class problems
- From: Ondra Cada <email@hidden>
- Date: Tue, 25 Jun 2002 14:00:00 +0200
On Tuesday, June 25, 2002, at 11:29 , Andy Lee wrote:
If testing for mutability is important enough, the right thing would be
for *Apple* to add an -isMutable method to the NSDictionary specification
(perhaps with my brute-force logic as its default implementation), and
implement -isMutable in NSCFDictionary, using whatever logic it uses now
to determine whether it's mutable.
As a matter of fact, I don't think so. The right thing would be to
dispense with the CoreFoundation thing, and return to the clean ObjC-based
Foundation, in which the class pattern is very natural and intuitive:
NSObject
ImmutableInterfaceClass
ImmutableHiddenSubclass1
...
ImmutableHiddenSubclassN
MutableInterfaceClass
MutableHiddenSubclass1
...
MutableHiddenSubclassM
That way there'd be no confusion and no problems at all. Bringing an
-isMutable method would really do no good to the cleanness and elegance of
Cocoa API.
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.