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!.POSTED!not-for-mail
From: "Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>
Newsgroups: comp.lang.ada
Subject: Re: multiple delay alternative
Date: Mon, 5 Mar 2018 18:37:13 +0100
Organization: Also freenews.netfront.net; news.tornevall.net;
 news.eternal-september.org
Message-ID: <p7jv89$lvj$1@dont-email.me>
References: <90838aa0-bd51-4913-b0cf-1ded5024c151@googlegroups.com>
 <1ea2c751-5a0a-47c2-aef4-96f137ee7628@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 5 Mar 2018 17:37:13 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
 posting-host="442056aebe5a1452e7fb8bca6c1bc206";
	logging-data="22515"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/7EJLmDaQSkyfr4RwxFSeltUqhboOYJcQ="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
In-Reply-To: <1ea2c751-5a0a-47c2-aef4-96f137ee7628@googlegroups.com>
Content-Language: en-US
Cancel-Lock: sha1:DHUEtCw/RISi/pRWqxn+egBXlMA=
Xref: reader02.eternal-september.org comp.lang.ada:50824
Date: 2018-03-05T18:37:13+01:00
List-Id: <comp.lang.ada>

On 03/05/2018 02:50 PM, Mehdi Saada wrote:
> It stands to reason that
> select
>>            delay <time>;
>>            <entry call>;
>>       or
>>            delay <time>;
>>            <entry call>;
>>       or
>>            delay <time>;
>>            <entry call>;
>>       end select;

This is confusing. Because it mentions entry calls, one might think it's a timed 
entry call, but that only allows a single delay alternative. And you don't 
usually have both a delay and an entry call in the same branch. A selective 
accept can have multiple delay alternatives, but has accept statements rather 
than entry calls. Again, you don't usually have a delay and an accept in the 
same branch.

> is not allowed for the caller, or you could try and call on multiple entrees at the same time, and pick up on of them... meaningless.

In Ada, you can do

select
    Entry_1;
then abort
    Entry_2;
end select;

Need more than 2? No problem; these can be nested

select
    Entry_1;
then abort
    select
       Entry_2;
    then abort
       Entry_3;
    end select;
end select;

The semantics of this seem somewhat confusing, though. While it's possible that 
only one of the entry calls will complete, it's also possible that any number of 
them will complete, including all of them.

-- 
Jeff Carter
"All citizens will be required to change their underwear
every half hour. Underwear will be worn on the outside,
so we can check."
Bananas
29