Re: Multiple interface inheritance workaround in Ada 95 / Ada 0x to satisfy a Java language advocate?

[Hyman Rosen <hyrosen@mail.com>]

Jim Rogers wrote:
> In Java all classes have an ultimate shared ancestor, the Object
> class.

True, but not really relevant since Object is above (below?)
the interfaces. If I have
	Class C extends Object implements I1, I2
then if I know my I1 is a C then I know it's also
an I2, but knowing that my I1 is an Object doesn't
tell me anything.

> procedure f(item : in I1_Access)
>    if item.all in I2'Class then
> 
> Note that this performs a lookup similar to what you describe.

But it's much simpler in Ada, since there is neither multiple
inheritance nor interfaces. For the test to be potentially true,
either I1 must be a subclass of I2, in which case the test
succeeds immediately, or I2 is a subclass of I1, in which case
we must actually examine item to see whether it inherits from
an I2-derived class. If I1 and I2 are unrelated, the test will
always be false, which is not true for C++ or Java.

C++ (and maybe Java also) has additional issues because the base
class might not be accessible due to non-public inheritance, or
there may be more than one I2 in the inheritance graph.