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

[Jim Rogers <jimmaureenrogers@worldnet.att.net>]

Hyman Rosen wrote:

> Jean-Pierre Rosen wrote:
> 
>> Yes. Or more exactly, the design pattern provides functions
> 
>  > that allow you to get an I1 or I2 view for a C object, and to
>  > go back from an I1 or I2 view back to the original C object.
> 
>>
>> And you are correct that this is not obvious to achieve.
> 
>  > That's what prompted me to make a paper of it!
> 
> Going back to the original object isn't quite the same thing.
> It's something of a red herring since this kind of thing is
> extremely rarely used, but you can't claim full conformity
> if you don't support it.
> 
> Here is what this kind of code looks like:
> 
> // Java
> void f(I1 i1) { if (i1 instanceof I2) { I2 i2 = (I2)i1; } }
> 
> // C++
> void f(I1 *i1) { I2 *i2 = dynamic_cast<I2 *>(i1); if (i2) { /*...*/ } }
> 
> As long as the underlying object has an accessible i2 in its
> inheritance graph, the conversion works, and the code does not
> need to know what the common ancestor class is, and will work
> for many different ancestor types.


In Java all classes have an ultimate shared ancestor, the Object
class.


> 
> This is accomplished by compiler magic. The compiler has access
> to the virtual tables and can search them for the presence of
> appropriate bases.
> 

I am not strong on C++ so I will deal with the Java example above.
All Java objects are accessed through references. This is equivalent
to having all Ada object accessed through access to class types.

The Ada equivalent for a tagged type is:

type I1_Access is access all I1'Class;
type I2_Access is access all I2'Class;

procedure f(item : in I1_Access)
    temp : I2_Access;
begin
    if item.all in I2'Class then
       temp := item;
    end if;
end f;

Note that this performs a lookup similar to what you describe.

Jim Rogers