Re: class cluster making: easy/lazy way to keep counterpart methods in sync?
Re: class cluster making: easy/lazy way to keep counterpart methods in sync?
- Subject: Re: class cluster making: easy/lazy way to keep counterpart methods in sync?
- From: Ben Dougall <email@hidden>
- Date: Sat, 21 Feb 2004 22:13:27 +0000
On Saturday, February 21, 2004, at 10:03 pm, Ondra Cada wrote:
On Saturday, Feb 21, 2004, at 22:36 Europe/Prague, Ben Dougall wrote:
has anyone got any ideas for keeping counter part concrete class
methods of a class cluster in sync while working on them? that's same
name, very similar implementations (except usually for direct
dealings with ivars, although other parts also will vary sometimes)
methods. a perfect situation, although i can't imagine how it'd be
possible, is to update one method and the others change too,
automatically, but only if it's the non-specific to ivar parts of the
method.
i want to make a class cluster that'll have potentially quite a few
concrete subclasses, and will also be pretty central to the app so
it's bound to require a lot of continual updating/tweaking -- and i
don't want to have to repeat the same updates/tweaks for each >
subclass.
any ideas?
Moving the methods which are same for all classes into the abstract
superclass, perhaps?
similar, not identical methods. like the NSNumber class that's on the
usual class cluster apple documentation page -- a class cluster because
the requirements for storage varies. and the ivars go in the subclasses
as do the methods that access them.
_______________________________________________
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.