|Keep It Simple, Stupid|
Re: Re: Re: Faking new() method in high-level packageby jreades (Friar)
|on May 08, 2002 at 23:13 UTC||Need Help??|
The problem that you're running into is that you're trying to run inheritance the wrong way (and possibly for the wrong reasons).
The short answer is that you can't have a high-level class be aware of a low-level class' functions without embedding those kind of ugly stubs in your code (at least, not that I know of).
The longer answer is this:
If all subclasses of class Utils will have a method called do_something(), then having a method stub (meaning a method that does nothing) is appropriate.
This would allow you to pass around objects belonging to any of Util's subclasses without worrying about their specific type. You would know that all Util subclasses could be made to perform some action simply by calling do_something(), whether or not the something to be done is the same for each subclass.
Looked at another way, if Util needs to be aware of a subclass' implementation of method then you've got the either the class hierarchy, or the class in which this method is declared, wrong. If calling Util::method() relies on Util::LowLevel::method(), then method() doesn't belong in the Util class since it doesn't work at that level of abstraction.
Does that make sense?
The other thing that is sounds like you are running into is the conflict between inheritance and composition.
You're trying to build a toolset to be offered by Util while relying on a LowLevel toolset supplied by a class that inherits from it. This sounds like a case for composition, not inheritance -- HASA vs. ISA. If your Util class needs a LowLevel toolset, then you might want to tackle it this way:
This approach probably only makes sense if you plan on having more than one toolset subclass (or you're doing a lot of OO work for little return). But now you have isolated Utils from the LowLevel Toolset class successfully and you could, for instance, make Toolset smart enough to instantiate itself differently (and return different low-level toolsets) based on the platform or something. This is one way to get a balance of abstraction and functionality, although there are, undoubtedly, many more