Re: Generic procedures and their parameters

[Georg Bauhaus <bauhaus@futureapps.de>]

Dmitry A. Kazakov wrote:

> But this all is independent on the question whether interface and
> implementation inheritances are different things. They are not. 

Suppose I have some complex number type C
having a lengthy division operation that requires
auxiliary components in the implementation.

Now I want a type of complex numbers just like C
but without a division operation.
One way to do so might seem to inherit a D from C,
and clear the division operation,

   type C is tagged private;
   ...
   procedure division(a, b: C; result: in out C);


   type D is new C with private;
   ...
   overriding
   procedure division(a, b: D; result: in out D) is null;

(Is there anything better than null BTW? It won't remove
division from D's interface...)
This will leave the auxiliary components of C in D.

But couldn't I do better? For example, by declaring
the interface I want, and then requesting that the needed
operations be "extracted" from C, dropping the division
stuff (provided there is a way to mark components as being
needed by only some set of operations.)

I will loose view conversions to C.
But if that is what I want? Just a composition of
the interface I need in some scope?