Re: multiple inheritance in Java
On 7/1/2013 10:16 PM, Stefan Ram wrote:
Eric Sosman <esosman@comcast-dot-net.invalid> writes:
only versions I know forbid multiple inheritance.
Because they forbid this, my question asked for a kind
of emulation of multiple inheritance.
Besides, I don't see where M.I. comes into the picture: You
seem to be asking about public fields and final fields, not
about how to merge multiple implementations and resolve their
potential conflicts.
I deal with the special case, when there are no conflicts,
and one just wants to merge (not literally) two classes.
Also, what are Position and Color?
Classes whose objects represent what is the English meaning
of position and color of a pixel, i.e., x and y, and r, g,
and b. I was hoping that this might become clear from the
examples given.
Okay. It might have been clearer if you'd chosen names that
weren't already taken -- although, one must admit, that's not easy
to do with Java's ever-growing namespace bloat. (Factoid: The HTML
*index* for the 7.0 API occupies eighteen meg!)
Still, I don't see the relevance of multiple inheritance to
your question, which seems to boil down to: "What are the trade-offs
in exposing fields vs. using accessors?" I think we can debate (have
debated) that matter at length without involving M.I. -- so it seems
I'm still missing your intent.
Could you explain how you feel the exposure-vs-accessor debate
would play out differently with multiple and single inheritance?
--
Eric Sosman
esosman@comcast-dot-net.invalid