Re: Ravenscar - Multiple Protected Entries

[Stephan Heinemann <zombie@cs.tu-berlin.de>]

> FIFO_Within_Priorities has nothing to do with it. There are 2 queues, 
> and each has only 1 task in it, so each task is at the head of its 
> queue. Each task is next to execute when its respective barrier becomes 
> True. And the language rules do not specify which task executes first. 
> So it is non-deterministic which task will execute next.

I am a littlebit confused... In 9.5.3 you can find the following
statement: "If calls from two or more queues are simultaneously
eligible for selection, the default entry queuing policy does not
specify which queue is serviced first.". The default queuing policy is
FIFO_Queuing. In section D.4 you can find the following: "When more
than one condition of an entry_barrier of a protected object becomes
True, and more than one of the respective queues is nonempty, the call
with the highest priority is selected. If more than one such call has
the same priority, the call that is queued on the entry whose
declaration is first in textual order in the protected_definition is
selected. For members of the same entry family, the one with the lower
family index is selected." Well, what shall I believe now?

Stephan