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.236.126.103 with SMTP id a67mr5754218yhi.4.1405586449258; Thu, 17 Jul 2014 01:40:49 -0700 (PDT) X-Received: by 10.182.186.34 with SMTP id fh2mr11020obc.21.1405586449133; Thu, 17 Jul 2014 01:40:49 -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!news.stack.nl!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!newspeer1.nac.net!border2.nntp.dca1.giganews.com!nntp.giganews.com!v10no1114784qac.1!news-out.google.com!bp9ni939igb.0!nntp.google.com!h18no2968482igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 17 Jul 2014 01:40:48 -0700 (PDT) In-Reply-To: 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> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <13ac2779-31e2-4ee9-879a-826335d2ae7d@googlegroups.com> Subject: Re: Timeouts in Ada From: NiGHTS Injection-Date: Thu, 17 Jul 2014 08:40:49 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:20992 Date: 2014-07-17T01:40:48-07:00 List-Id: On Thursday, July 17, 2014 3:38:40 AM UTC-4, J-P. Rosen wrote: >=20 > This kind of select is called a timed entry call. It tries to rendezvous >=20 > with Password_Server; if the server accepts the rendezvous before 10.0 >=20 > seconds, the statements after the entry call are executed and the "or" >=20 > part is ignored. If the server doesn't accept the rendezvous within 10.0 >=20 > seconds, the rendezvous request is cancelled and the statements in the >=20 > "or" part are executed. >=20 I was mainly confused by the fact that the delay command was placed inside = the body of a fork in the path of logic, making it seem as though in order = to satisfy the syntax it had to do things concurrently. ARM seems to imply = that it expects a delay in the body (first command?) as a condition to dete= rmine which path to take. I'm still a little fuzzy on the mechanics but I'm= sure this will clear up as I do some more reading on the C variant.