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
X-Received: by 10.224.134.195 with SMTP id k3mr17367916qat.4.1405619887667;
        Thu, 17 Jul 2014 10:58:07 -0700 (PDT)
X-Received: by 10.182.105.101 with SMTP id gl5mr303115obb.4.1405619887538;
 Thu, 17 Jul 2014 10:58:07 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!j15no1251657qaq.0!news-out.google.com!bp9ni941igb.0!nntp.google.com!h18no3196222igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 17 Jul 2014 10:58:07 -0700 (PDT)
In-Reply-To: <lybnsnyko5.fsf@pushface.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=73.179.102.101;
 posting-account=wEPvUgoAAABrLeiz_LRhQ3jeEhyfWVMH
NNTP-Posting-Host: 73.179.102.101
References: <50bdb713-7ce1-411b-810b-9bdee1d26b7a@googlegroups.com>
 <cd50cff5-a37a-4c41-a091-cc6c0aae6c8f@googlegroups.com>
 <7581b098-ea30-4b34-a51e-2f0dd5a57563@googlegroups.com>
 <lybnsnyko5.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <131b545e-185b-4c4a-8a72-c627ff507138@googlegroups.com>
Subject: Re: Timeouts in Ada
From: NiGHTS <nights@unku.us>
Injection-Date: Thu, 17 Jul 2014 17:58:07 +0000
Content-Type: text/plain; charset=ISO-8859-1
X-Received-Bytes: 2952
X-Received-Body-CRC: 2398426758
Xref: news.eternal-september.org comp.lang.ada:21007
Date: 2014-07-17T10:58:07-07:00
List-Id: <comp.lang.ada>

On Thursday, July 17, 2014 1:11:54 PM UTC-4, Simon Wright wrote:
> 
> > So even if the entry call takes an hour, it will still wait the full
> 
> > hour until it completes before entering the "or delay" section? This
> 
> > is what I am understanding so far.
> 
> 
> 
> After the entry call has been accepted, the timeout is cancelled; Adam's
> 
> pseudocode had Wait_For_Rendezvous_To_Complete at that point. It could
> 
> wait for days to complete (not that that's a good idea).
> 
> 
> 
> > Also, can two entry calls be placed like this?
> 
> >
> 
> >     select call_1(params)
> 
> >         ...
> 
> >     or call_2(params)
> 
> >         ...
> 
> >     or delay 10
> 
> >         ...
> 
> >     end select
> 
> >
> 
> > If so, how would it know which finishes first without having them run
> 
> > concurrently? Don't see a point in having them run one after the
> 
> > other.
> 
> 
> 
> Not allowed: ARM 9.7.2 [1].
> 
> 
> 
> > I have also seen the select used with an "else". What exactly is the
> 
> > difference between "or" and "else"? Is "else" used when a "delay" is
> 
> > not involved? Otherwise I don't see the point in the "else" path.
> 
> 
> 
> This is in ARM 9.7.3. If the entry_call_alternative (the part after the
> 
> select) can't be accepted immediately, the else part is executed.
> 
> 
> 
> [1] http://www.ada-auth.org/standards/12rm/html/RM-9-7-2.html

Again, your links were very helpful. It led me to the following discussion on this topic which I feel completely satisfies my curiosity on this subject.

http://archive.adaic.com/standards/83lrm/html/lrm-09-07.html

Thank you all for bearing with me and taking the time to help me with this.