Re: Finalization of library level tasks

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 26/04/2018 02:04, Randy Brukardt wrote:
> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message
> news:pb74sr$1cmf$1@gioia.aioe.org...
>> On 18/04/2018 10:52, Egil H H wrote:
>>> Undefined?
>>>
>>> 9.9(2), "a task is callable unless it is completed or abnormal"
>>> 9.3(5), "A task is said to be completed when the execution of its
>>> corresponding task_body is completed"
>>
>> OK, it is defined enough to confirm that T'Callable cannot be used to
>> break finalization deadlock.
> 
> Of course it can: you test T'Callable of your parent task, *not* of
> yourself. If that parent is the environment task, use the
> Task_Identification version.

No, because the parent task is not going to terminate.

The problem is to test if the current task is awaited to terminate in 
order to have an equivalent of:

    loop
       select
          terminate;
       else
          null;
       end select;
       -- Do a portion of work
    end loop;

There is no solution to this below the library level where the 
environment task hack works.

Under the library level an access to the task must be used *and* this 
pointer type must be declared one level up the future master of the 
task. I.e. it cannot be local in the scope where the object creating the 
task lives. This will deadlock as mandated by the RM.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de