Re: Type in allocator has deeper level than designated class-wide type

[Adam Beneschan <adam@irvine.com>]

On Jun 14, 1:01 am, Adrian Hoe <aby...@gmail.com> wrote:
>
> But this defeats my implementation intention which the size and the
> type of its data array can only be determined during runtime. Any
> suggestion?

There was no reason to change the generic parameters to High_Cloud, or
to change the type of the Data component from Data_Array to Item.  As
I tried to explain, your problem had nothing to do with arrays.  The
problem has to do with where the Element_Record type extension is
declared, which has to do with where the High_Cloud generic is
instantiated.  In your latest example, you instantiated it directly in
a library package, Hen, so there won't be a problem.  If you
instantiate it inside a procedure, there will be a problem.  But the
types of the components don't matter.

If it *does* make a difference---i.e. if declaring Data as a
Data_Array instead of an Item makes things fail, even if High_Cloud is
still instantiated directly inside Hen---then I believe the problem is
with your compiler, and you need to contact your compiler vendor and
file a bug report.

                                  -- Adam