Overriding Default_Component_Value in derived array type

[Niklas Holsti <niklas.holsti@tidorum.invalid>]

I'm seeing behaviour that looks strange to me when I derive an array 
type from another and use a Default_Component_Value aspect that tries to 
override the corresponding aspect of the parent type. The parent's 
default value is used also for the derived type, that is, the aspect 
definition for the derived type has no effect, it seems.

This is on macOS Mojave (10.14.6), GNAT Community 2019 (20190517-83).

An example:

       type Number is range 1 .. 15;

       type Arr_2 is array (3 .. 5) of Number
       with Default_Component_Value => 2;

       type Arr_6 is new Arr_2
       with Default_Component_Value => 6;

       A2 : Arr_2;
       A6 : Arr_6;

Printing out the default values of A2 and A6 I get 2's for both. I 
expected 2's for A2 and 6's for A6, as I read the RM.

Overriding Default_Value for a derived integer type works as expected, 
as does overriding a Default_Value for the component type with a 
Default_Component_Value for the array type.

For the array type derivation, if the parent array type has no 
Default_Component_Value then the Default_Component_Value for the derived 
type is effective. That is, in the above example, if I remove the 
Default_Component_Value from Arr_2, then A2 contains garbage as 
expected, and A6 contains sixes.

Bug or feature?

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .