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

["Randy Brukardt" <randy@rrsoftware.com>]

<tmoran@acm.org> wrote in message news:kqtn1d$2ua$1@speranza.aioe.org...
...
>> 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

Janus/Ada unfortunately doesn't do this consistently. This is a hard 
problem, because the compiler doesn't know how big the stack will be at 
runtime, and adding the level of indirection costs a bit of performance. So 
you could run into trouble if the program uses a bunch of medium-sized but 
statically-sized objects that collectively overflow the stack.

In the OP's program, however, all of the objects are dynamically-sized; in 
that case, Janus/Ada always uses a level of indirection and only uses the 
stack for very small objects, so one gets the automatic heap-based 
allocation (and deallocation) seen here.

                                                    Randy.