Re: Inheritance versus Interfaces...

Post #14,142 by JimWeirich 10/19/01 7:30:48 AM Reply	Re: Inheritance versus Interfaces... I've always had a problem with the idea of multiple inheritances of classes when they overlap, and I like the way that Java deals with that - through Interfaces as opposed to Inheritance. What do you do when interfaces overlap? -- -- Jim Weirich jweirich@one.net [link\|http://w3.one.net/~jweirich\|http://w3.one.net/~jweirich] --------------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)
Post #14,182 by Arkadiy 10/19/01 1:10:03 PM Reply	Re: Inheritance versus Interfaces... Use explicit naming like objvar.Interface1.do() and objvar.Interface2.do() ? Just a guess, I've never run into this problem.
Post #14,229 by inthane-chan 10/19/01 6:49:00 PM Reply	That's the basic of it. It comes in handy when you have two Interfaces, both of which need to be implemented within a class, which share an overlapping function name. Admittedly, this will generally only happen if somebody's a piss-poor designer, but still, it's nice to have the functionality around. "He who fights with monsters might take care lest he thereby become a monster. And if you gaze for long into an abyss, the abyss gazes also into you." - Friedrich Nietzsche
Post #14,985 by kelzer 10/24/01 2:55:03 PM Reply	Re: Inheritance versus Interfaces... No, there is no clashing because the interfaces have no implementation code. So if a class implements two different interfaces, and both interfaces declare a "void run()" method, as long as you implement "void run()" you're OK.

Welcome to IWETHEY!