Re: Private or public task ?

["Hibou57 (Yannick Duchêne)" <yannick_duchene@yahoo.fr>]

On 10 fév, 09:17, Maciej Sobczak <see.my.homep...@gmail.com> wrote:
> > There are two kinds of blockings: bounded and unbounded. The idea is
> > that when computing a time budget, you can account for bounded
> > blockings, but not unbounded ones.
> > The "potentially blocking" phrase should be understood as really meaning
> > unbounded.
>
> Well, I know what you try to convey, but there are traps:
>
>    delay Some_Static_Constant;
>
> Is it bounded or unbounded?
>
> As far as WCET (or any other time-based analysis) goes, the above can
> be accounted for statically. Still, it is a no-no within any protected
> operation.
Interesting enigma

I would say Bounded, as it is predictable.
... as long as the delay is short, otherwise it will break the other
rule stating that a protected operation should be fast to execute.

If I try to have a delay X.Y in a protected operation, GNAT just warns
me “ potentially blocking operation in protected operation ”, while
the program is still compiled.

You've said “ it is a no-no within any protected ” : do you get a
compilation error when you do the same ?

I've not seen anything in the Rationale nor in the ARM which
explicitly disallow it anyway (but as these are long pages I should
later read again, I may have miss it).