Re: Delayed deallocation of non-terminated task in Gnat?

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

Adam Beneschan <adam@irvine.com> writes:

> Actually, I just found this in the Ada 83 manual (13.10.1(8)):
>
> "If X designates a task object, the call FREE(X) [where FREE is an
> instance of Unchecked_Deallocation] has no effect on the task
> desginated by the value of the task object.  The same holds for any
> subcomponent of the object designated by X, if this subcomponent is a
> task object."
>
> This language got dropped in Ada 95, but I think it was intended that
> these still be the semantics, for a task without discriminants (Ada 83
> did not allow task discriminants).  I'm not sure why the language was
> omitted; ...

It might have to do with the fact that task values don't formally
"designate" anymore.  Anyway, it doesn't need to say anything.
If it doesn't say anything happens to the task, then nothing
happens -- it just keeps running.  It doesn't say U_D waits
for it to terminate.  It doesn't say U_D aborts it.  It doesn't
say that U_D should set all variables to 17.  So none of these
things happen.

> One thing that bothers me a bit, although I don't know if it bothers
> me enough to request an RM change:

I suggestion you refrain.  ;-)  This sort of nitpicking is just
a waste of time for the ARG.  Any wording change wouldn't affect
the behavior of any programmer, nor any implementer, so why
bother?

- Bob