Re: Classwide Parameter?

[Matthew Heaney <matthewjheaney@earthlink.net>]

matthias_k <nospam@digitalraid.com> writes:

> I have experimented a little, and I can't really figure out what I need
> classwide parameters for.

Class-wide objects dispatch their primitive operations.  The call is
dynamically bound, not statically bound.


> Consider this code:
> 
> package Shape_Pkg is
>     type Shape is abstract tagged null record;
>     procedure Draw (obj: Shape);  -- try adding "is abstract" here
> end;
> 
> package Circle_Pkg is
>     type Circle is new Shape with null record;
>     procedure Draw (obj: Circle);
> end;
> 
> ...
> 
> procedure Test is
>     c: Circle;
> begin
>     Draw( c ); -- calls Circle_Pkg.Draw
> end Test;
> 
> ------------
> 
> Now, if I change Shape_Pkg.Draw's formal parameter to Shape'Class,
> what's the difference? In both cases it's legal to call Draw on a
> Circle.

The call to draw in your example above is statically bound.  A better
way to see what's going on is to do this:

procedure Test_Draw (S : Shape'Class) is -- class-wide type
begin
   Draw (S);  -- call is dynamically bound
end;

We can now rewrite your example:

procedure Test is
   C : Circle;
begin
   Test_Draw (C);  --will call Circle_Pkg.Draw
end;


A better example is adding different types that derive from Shape ("are
in the Shape class," in Ada-speak):

procedure Test is
   C : Circle;
   S : Square;
   T : Triangle;
begin
   Test_Draw (C);  --will call Circle_Pkg.Draw
   Test_Draw (S);  --calls Square_Pkg.Draw
   Test_Draw (T);  --calls Triangle_Pkg.Draw
end;