Re: Super's Super?
Re: Super's Super?
- Subject: Re: Super's Super?
- From: Marco Scheurer <email@hidden>
- Date: Sun, 12 May 2002 17:18:53 +0200
On Saturday, May 11, 2002, at 11:02 PM, Jeff LaMarche wrote:
Maybe your class should be the subclass of the super-super class
instead of its current superclass?
Unfortunately, no. My first thought was exactly the same - perhaps the
design was wrong.. but in this case, the class is most definitely
appropriately a child of its superclass, there's just this one method
where the behavior needs to be totally different, but I still need the
functionality that the grandparent object (a non-concrete class that is
the root of my framework's heirarchy) provides. =(
I think that your design IS wrong.
You have this class hierarchy:
A
B
C
You want one of C methods to inherit A's implementation instead of B's.
You need another abstract class:
A
B-abstract
B-concrete
C
where B-abstract does not override your method.
marco
Marco Scheurer
Sen:te, Lausanne, Switzerland
http://www.sente.ch
_______________________________________________
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.