From: Victor Porton <porton@narod.ru>
Subject: Re: Deallocating an object twice
Date: Sat, 26 Jul 2014 23:02:25 +0300
Date: 2014-07-26T23:02:25+03:00 [thread overview]
Message-ID: <lr11gd$log$2@speranza.aioe.org> (raw)
In-Reply-To: lr1142$log$1@speranza.aioe.org
Victor Porton wrote:
> If I understand correctly, it is an undefined behavior (or is it called
> unbounded error?) if a pool access is deallocated twice with
> Unchecked_Deallocation.
>
> I think it should be a Program_Error (if checks are on).
>
> Why was not this done even in Ada2012 (not speaking about older Ada)?
>
> It's bad.
>
> Or is it done and I just miss it?
The same should be done if attempt to deallocate an access which never has
been allocated (for example, if it is an aliased object on the stack).
--
Victor Porton - http://portonvictor.org
next prev parent reply other threads:[~2014-07-26 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 19:55 Deallocating an object twice Victor Porton
2014-07-26 20:02 ` Victor Porton [this message]
2014-07-27 2:39 ` Randy Brukardt
2014-07-27 2:42 ` Randy Brukardt
2014-07-27 8:31 ` Simon Wright
2014-07-27 11:30 ` anon
2014-07-27 12:47 ` Peter Chapin
2014-07-27 15:29 ` Stephen Leake
2014-07-27 15:34 ` Victor Porton
2014-07-28 15:15 ` Stephen Leake
2014-07-28 16:15 ` Simon Wright
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox