From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: some remarks and requests for confirmation on tasks and protected objects Date: Tue, 6 Mar 2018 14:25:36 -0600 Organization: JSA Research & Innovation Message-ID: References: Injection-Date: Tue, 6 Mar 2018 20:25:36 -0000 (UTC) Injection-Info: franka.jacob-sparre.dk; posting-host="rrsoftware.com:24.196.82.226"; logging-data="28710"; mail-complaints-to="news@jacob-sparre.dk" X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246 Xref: reader02.eternal-september.org comp.lang.ada:50857 Date: 2018-03-06T14:25:36-06:00 List-Id: "Dmitry A. Kazakov" 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.