Re: [Ravenscar] run tasks on events

[Sebastian Hanigk <hanigk@in.tum.de>]

Niklas Holsti <niklas.holsti@tidorum.invalid> writes:

> Anh Vo wrote:
>> It is not true. Protected entry, implemented in Transient
>> Signals for example, can suspend/release multiple tasks.
>
> True in unrestricted Ada (an entry queue can hold many tasks), false
> under the Ravenscar profile (maximum one task waiting on an entry). If
> you use protected objects to trigger tasks, you need one object per
> task.

Argh. Seems I was too early in my reply to Anh Vo ...

Shouldn't there be a constraint error?

> Note that under the Ravenscar profile, one generally needs one
> protected object per (sporadic) task, anyway, to trigger that task
> when required. This protected object can easily be extended with a
> boolean control variable such that the entry triggers the task only in
> the appropriate modes or phases.

I hadn't included the Profile pragma in all my source files, so I'm
assuming that the successful test earlier on was due to not complying
with the Ravenscar profile. Having put the pragma directives into the
source code, now only one of the waiting tasks resumes/suspends.

> On the other hand, personally I'm a bit skeptical about triggering
> certain tasks only in certain modes. I suspect that most systems could
> as well keep the same set of active tasks, and just make the tasks do
> different things in different modes, using plain old "if then else" in
> the task body.

Well, I found the signaling/scheduling concept very elegant; now it
seems my best bet would be a check inside each task's loop if the
respective conditions evaluate to True, otherwise simply delay until the
next period.


Thank you for your help!

Sebastian