Re: Q: Stopping a task running a long simulation

[Gautier write-only <gautier_niouzes@hotmail.com>]

On 12 mar, 01:24, tmo...@acm.org wrote:
> > 'Compute' has a generic 'Feedback' procedure for showing progress.
> > I could with that way give a Boolean, user_abort, to 'Feedback', and
> > 'Compute' would stop when an ad-hoc exception is raised, and return
> > normally on its own.
>
>   Think of a motor and its control panel.  The panel does read-only access
> to certain information in the motor, its speed for instance, which the
> panel displays.  The panel can also write certain information, like Stop,
> to a switch that the motor periodically (every rotation?) checks.  Compute
> is your motor and the GUI is the control panel.  Progress information
> is regularly written by Compute to a record, which is periodically
> read by the GUI, and control information is written as needed by the
> GUI and regularly read by Compute.

Thanks - it is a perfect metaphore. And be reassured, I have no
trouble programming this. My question is: would you recommend that way
(have a mechanism to tell the motor to stop) in order to have a chance
in a reasonable time to stop the "runner daemon" task in its turn ? I
am tempted to do so. I was just exploring possibilities of stopping
the daemon and the motor in a direct and less polite way, but still
good Ada practice.
Gautier