Re: Dynamich Dispatching...

[Ludovic Brenta <ludovic.brenta@insalien.org>]

"Rick Santa-Cruz" writes:
> Hi,
>
> I know what to understand about Dynamic Dispatching, but with the
> following example in Ada I have some problems to understand the
> whole thing:

RM 3.9.2(20, 21) state that the only factor that determines which
subprogram (method) is called is the tag of the operand (i.e. the
actual run-time type).  Whether or not the subprogram is visible at
the point of call is irrelevant.  Thus:

package Objects is
   type Object is tagged private;
   procedure Draw (O : in Object); -- a primitive suprogram
   procedure Draw_Any (O : in Object'Class); -- not a primitive
private ...
end Objects;

package body Objects is
   ...
   procedure Draw_Any (O : in Object'Class) is
   begin
      Draw (O); -- dynamic dispatching call
   end Draw_Any;
end Objects;

with Objects;
package Circles is
   type Circle is new Objects.Object with private;
   procedure Draw (C : in Circle); -- overrides Objects.Draw
private ...
end Circles; 

with Circles;
with Objects;
procedure Main is
   C : Circles.Circle;
begin
   Objects.Draw_Any (C);
end Main;

Even though the procedure Draw_Any does not see the package Circles,
dynamic dispatching still causes Circles.Draw to be called.  This is
good; it means that Draw_Any does not have to be aware of the
existence of all types derived from Objects.Object.  This in turns
means that new derived types can be added to the program without
changing Draw_Any.

-- 
Ludovic Brenta.