class cluster making: easy/lazy way to keep counterpart methods in sync?
class cluster making: easy/lazy way to keep counterpart methods in sync?
- Subject: class cluster making: easy/lazy way to keep counterpart methods in sync?
- From: Ben Dougall <email@hidden>
- Date: Sat, 21 Feb 2004 21:36:15 +0000
the answer to this is probably there's no way (at least not without a
lot of work), but no harm in asking -- maybe someone's already got a
solution? regarding making and working on your own class cluster:
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?
thanks, ben.
_______________________________________________
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.