Re: memory management in Ada: tedious without GC?

[Matthew Heaney <mheaney@on2.com>]

On May 19, 5:21 pm, Maciej Sobczak <see.my.homep...@gmail.com> wrote:
>
> Note also that it prevents some obvious optimizations like avoiding
> memory allocator round-trip when for example short container is
> assigned to a longer one, which already has enough place for RHS.

Right.  I suppose if a strong guarantee is necessary, then you could
make the type limited and then provide an Assign operation.


> The memory is lost.
> OK, it is still managed by the relevant storage pool - but if the pool
> itself is not dynamically scoped (or the scope is just too wide), then
> it is effectively a leak.

I guess in that case you could use an indefinite type (limited or non-
limited -- it doesn't matter anymore in Ada05) and allocate the object
on the stack.

declare
  O : T := Initialize (...);
begin

In the event of an exception during initialization, the stack would
get unwound in the normal way and there would be no memory leak.

Cheers,
Matt