Re: dinamic object reclamation

[Ted Dennison<dennison@telepath.com>]

In article <9oa69d$6ej$1@ns.omskelecom.ru>, Anisimkov says...
>  procedure act (i : integer)
>  is
>      type block is array (1 .. 1024) of integer;
>      type block_ptr is access all block;
>      ptr : block_ptr;
>  begin
>      ptr := new block;
>      ptr (ptr'LAst) := i;
>      put (integer'image(I));
>  end;
>Is memory allocated by
>      ptr := new block;
>have to be freed automatically after leaving of procedure act ?

I believe compilers are allowed, but not required, to garbage collect here. If
you want to force the issue w/o using Unchecked_Deallocation, specify a fixed
size for Block_Ptr's storage pool. For example, in the above code, add the line:

for Block_Ptr'Storage_Size use 4098;

and you should be OK (If you get Storage_Error, jack up the number a bit). You
won't be able to allocate any more than the specified number of bytes this way,
but a conforming compiler *will* reclaim the storage when the access type goes
out of scope. (LRM 13.11-18).


---
T.E.D.    homepage   - http://www.telepath.com/dennison/Ted/TED.html
          home email - mailto:dennison@telepath.com