Re: Allocators and exceptions

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

"Randy Brukardt" <randy@rrsoftware.com> wrote in message
news:fc9p94$rt6$1@jacob-sparre.dk...
...
> Because Ada *requires* storage leakage in such cases (although some
> compilers ignore the language definition and finalize anyway). An
allocated
> object cannot be finalized until it's *type* is finalized or until an
> Unchecked_Deallocation is called -- and an Unchecked_Deallocation is not
> going to be called if a constructor propagates an exception. So the
> (inaccessible) object is supposed to hang around for a long, long time.

For what it's worth, the rule in the RM is 7.6.1(10), which says:

"Immediately before an instance of Unchecked_Deallocation reclaims the
storage of an object, the object is finalized. If an instance of
Unchecked_Deallocation is never applied to an object created by an
allocator, the object will still exist when the corresponding master
completes, and it will be finalized then."

                      Randy.