Re: multiple inheritance in Java
On 7/2/2013 6:02 AM, Stefan Ram wrote:
Eric Sosman <esosman@comcast-dot-net.invalid> writes:
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.
When an object O exposes two public fields of two classes P and Q,
this has some of the benefits that mutiple inheritance from both
P and Q would have, while one does not tediously has to code
a lot of delegating methods in this object O.
(When I really implement this, P and Q actually are interfaces,
but the during the creation of O an implementation of those
interfaces is assigned to their corresponding fields in O.)
I still don't see the relevance of M.I. to the question.
Thought experiment: How would anything change if you were to
remove Q from the scenario altogether?
This might also be called ?poor man's multiple inheritance?.
I'm not sure why anyone would use that term for "making a
field public."
--
Eric Sosman
esosman@comcast-dot-net.invalid