Re: tagged types extensions - language design question

["Vladimir Olensky" <vladimir_olensky@yahoo.com>]

Andy wrote in message <3892BABB.290D@nospam.com.tj>...

>Although it is good practice to have each child class type in its
>own package, if the intermediate type is just to allow a double
>extension (one public, one private), why not just do so in the one
>package, something like:
>
>-- Root class
>--
>package P1 is
>    type Root is abstract tagged null record;
>    procedure Method (X : in Root) is abstract;
>end P1;
>
>-- Child class
>--
>package P1.P2 is

>
>    -- public extension
>    -- this is abstract so we don't have to override any
>   -- abstract operations defined by the paraent class.
>   --
>    type Intermediates is abstract new P1.Root with record
>        F : Float;  -- etc.
>    end record;
>
>    type Objects is new Intermediates with private;
>
>    procedure Method (X : in Objects);
>
>private
>
>    type Objects is new Intermediates with record
>        I : Integer;  -- etc.
>    end record;
>
>end P1.P2;


Yes, that's fine.

Creating one intermediate type with public attributes
is not a big deal.
It looks strange at first glance that one can not extend both
public and private part in one step but then one get used to
it and it does not seem to be a problem any more.

Regards,
Vladimir Olensky