Re: some remarks and requests for confirmation on tasks and protected objects

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2018-03-06 21:25, Randy Brukardt wrote:
> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message
> news:p7m5n3$fp6$1@gioia.aioe.org...
> ...
>> I think this is related to inability to change entry call parameters. That
>> is the only practical use case for families.
> 
> Not sure fo the context here, but IMHO the only practical use case for a PO
> families is when you need to refer to a parameter in a barrier. (Unlike a
> task, there is only one body for the entire family, so the family index
> works like a parameter that can be used in a barrier.)

Right, I am using it for waiting for a condition which cannot be used in 
a barrier. There is a family indexed by Boolean guarded by the expression

    Index = Toggle

When the awaited condition is not satisfied the call is requeued to the 
complementary entry (not Index).

When the condition is about to change Toggle is toggled and the 
complementary entry gets open.

> I'm not sure there is any real use case for a task family.

I never used that, maybe something like above.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de