Re: Termination of tasks waiting on a protected queue

["Alejandro R. Mosteo" <mosteo@gmail.com>]

On Monday, May 19, 2014 1:05:59 AM UTC+2, Brad Moore wrote:
> On 14-05-18 01:32 AM, Natasha Kerensikova wrote:
> 
> > The problem is, how to terminate cleanly the worker tasks in a
> 
> > non-Ravenscar environment when the main application is completed?
> 
> >
> 
> >  From my understanding of ARM 9.3, I need a terminate alternative in the
> 
> > worker tasks. But those can only exist in selective accepts, so I have
> 
> > to turn things around and make the task wait for one of its entries to
> 
> > be called, rather than wait for an external protected entry.
> 
> >
> 
> > But then, how can a worker task entry be used to solve my problem? A
> 
> > protected operation cannot call a task entry, because it's potentially
> 
> > blocking. The job generator cannot call the entry directly, because it
> 
> > would block when the task is not ready, so I still need a queue between
> 
> > the generator and the worker task.
> 
> 
> 
> A protected entry can however requeue to a task entry.
> 
> 
> 
> I was faced with a similar problem in the non-Ravenscar task pools in 
> 
> Paraffin.
> 
> 
> 
> I did not want the programmer to have to call some protected subprogram 
> 
> to trigger the task pool to terminate. 

Could an atomic boolean be used to avoid a protected object? Given that after it being set it wouldn't be unset, and there's no race condition, I wonder.