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

["Randy Brukardt" <randy@rrsoftware.com>]

"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.)

I'm not sure there is any real use case for a task family. The need to write 
separate accepts for each value makes it impractical to have more than a 
handful.

Moral: the only commonality between task and PO families is the way that 
they're called. The underlying implementation (both in Ada source and in the 
compiled program) is completely different, and thus so are the use cases.

                                      Randy.