Re: Finalization of library level tasks

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

On 18/04/2018 23:29, J-P. Rosen wrote:
> Le 18/04/2018 à 16:52, J-P. Rosen a écrit :
>> OK. You were actually quite close... Use a killer task (with the same
>> master as your worker) like this:
>>
>> task Killer is
>>     entry Never_Called;
>> end Killer;
>>
>> task body Killer is
>> begin
>>     accept Never_Called;
>> exception
>>     when Tasking_Error =>
>>       -- Kill the other task
>> end Killer;
>>
>> Hint: when the master completes, Tasking_Error is raised in all tasks
>> waiting on entries that depend on that master.
> Sorry, my mistake. Typed too fast from an old trick I used... It's the
> other way round. When a task completes, it raises Tasking_Error in the
> tasks waiting on its entries.
> 
> So, you can wait for the completion of a task without busy waiting by
> calling an entry of the task that is never accepted, and handling
> tasking_error.

But how to complete that task in the first place? The scenario of task 
termination you described in this thread before specifically precludes 
any task to complete in the event of master waiting them to complete. It 
is a deadlock built into the language.

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