Re: Pitfall: freeing access discriminants

[Robert A Duff <bobduff@shell01.TheWorld.com>]

porton@ex-code.com (Victor Porton) writes:

> In my understanding there may be several standard access pool and the 
> pool for access Integer and for Integer_Ptr may be different. Isn't it 
> so?

That's correct.  If you don't say "for T'Storage_Pool use...", the
implementation can use any storage pool it likes.  It can put all such
types in the same global heap, or it can create a new pool for each
type, or anything in between.

I think what you want is something like:

    type Int_Ptr is access Integer;

    type T(X: Int_Ptr) is new Limited_Controlled...

Then you can safely deallocate X using an Unchecked_Deallocation for
Int_Ptr.

- Bob