Re: Thick bindings to a C library and gnattest: suggestions?

[tmoran@acm.org]

> > (Aside: in a world in which GB of RAM are common, it seems odd for a
> > language to require explicit heap allocation, and the associated memory
> > management, for objects that fit in memory, but not in the stack. Surely
> > it would be better for the language to allow the developer to simply
> > declare the object, and for the compiler to decide where it will fit, and
> > allocate it and manage its memory appropriately. A means to disable
> > automatic heap allocation would be needed for systems that disallow heap
> > allocation.)
>
> Amen! I've been saying that for 30+ years; perhaps someday it will really be
> true in commonly used compilers.
>
>                              Randy.
  I notice that when I tried the OP's declare with the Janus Ada compiler
it ran for up to a little over 800MB for the array, then above that it
said:
** Unhandled STORAGE_ERROR
   Heap Overflow
On Line Number 16 In TRYBIG.DOIT
Called from line number 27 In TRYBIG
suggesting that the compiler was
> > decide where it will fit, and
> > allocate it and manage its memory appropriately.