Re: Mutable class problems
Re: Mutable class problems
- Subject: Re: Mutable class problems
- From: Lance Bland <email@hidden>
- Date: Tue, 25 Jun 2002 10:25:30 -0400
On Tuesday, June 25, 2002, at 08:00 AM, Ondra Cada wrote:
NSObject
ImmutableInterfaceClass
ImmutableHiddenSubclass1
...
ImmutableHiddenSubclassN
MutableInterfaceClass
MutableHiddenSubclass1
...
MutableHiddenSubclassM
That is one way, but it also forces the class structure to correspond to
only one parameter, which is a hefty penalty. We designed mutability
that way (in reverse) for some of our object classes and found it was
too cumbersome in the long run so we redesigned away from that
structure. Another way is to place attributes into a attribute related
key of the dictionary so attributes aren't forced by obj-c. I've always
thought of dictionaries as a way to get away from obj-c's class rigidity
and applying rigidity on a dictionary with an obj-c convention seems
counter to the use of dictionaries. The actual solution depends on the
problem.
-lance
------------------------------------
Lance Bland
mailto:email@hidden
web charts at
http://www.vvi.com/products/chart
_______________________________________________
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.