Re: How to make a task wait and resume ?

[reinert <reinkor@gmail.com>]

I suspected to be missing something :-)

In my case, a user is normally actively interacting with the actual program
which is about treating a large sequence of images. The user can start/stop 
a task which reads in images upfront to avoid waiting time. If the computer
is weak (small ram) he/she sometimes has to stop the reading (and the program automatically "clean" memory) and probably resume later. Hence the "synchronization" here is not with other tasks.

reinert

torsdag 17. januar 2019 23.28.17 UTC+1 skrev Randy Brukardt følgende:
> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message 
> news:q1qe0o$1te0$1@gioia.aioe.org...
> > On 2019-01-17 17:21, reinert wrote:
> >
> >> I have used a protected object to control (from "outside")
> >> wait/resume of a task. It works, but is it good practise?
> >
> > Why not? In other cases you might use a task entry instead of protected 
> > object.
> 
> You could also use the built-in types for that purpose, see D.10, 
> Synchronous Task Control.
> 
> ...
> > If the pulse event to release several tasks it is a bit more complicated. 
> > An example is in the Simple Components.
> 
>  For that, you might want to use a Synchronous Barrier, see D.10.1.
> 
> For me, I would try to do this as part of other necessary synchronization, 
> using usual task or protected operations. One rarely wants to have a task 
> wait in a vacuum. If I had to do it by iteself, however, I'd probably use 
> one of the built-in types (have to implement them in Janus/Ada, first, 
> though :-).
> 
>                           Randy.