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.182.119.129 with SMTP id ku1mr18315609obb.20.1405586107394;
 Thu, 17 Jul 2014 01:35:07 -0700 (PDT)
X-Received: by 10.182.226.233 with SMTP id rv9mr281936obc.6.1405586107135;
 Thu, 17 Jul 2014 01:35:07 -0700 (PDT)
Path: 
 border1.nntp.dca1.giganews.com!nntp.giganews.com!h18no1568598igc.0!news-out.google.com!gf2ni864igb.0!nntp.google.com!h18no1568592igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 17 Jul 2014 01:35:06 -0700 (PDT)
In-Reply-To: <lyfvi0xy0w.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>
 <lyfvi0xy0w.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <38c21492-9876-4207-8be1-33e53c56bc12@googlegroups.com>
Subject: Re: Timeouts in Ada
From: NiGHTS <nights@unku.us>
Injection-Date: Thu, 17 Jul 2014 08:35:07 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: number.nntp.dca.giganews.com comp.lang.ada:187642
Date: 2014-07-17T01:35:06-07:00
List-Id: <comp.lang.ada>

On Thursday, July 17, 2014 3:08:47 AM UTC-4, Simon Wright wrote:
>=20
> You're actually asking HOW the compiler does it; ARM 9.7.1(15ff)[2] says
>=20
> WHAT the compiler has to arrange to happen to meet the standard.
>=20
> [1] http://www.unix.com/man-page/opensolaris/3c/cond_wait/
>=20
> [2] http://www.ada-auth.org/standards/12rm/html/RM-9-7-1.html#p15

These links were very helpful. I had almost forgotten about the ARM when fa=
ced with this question. Also, the C explanation makes sense to me -- I supp=
ose the Ada select/or/else is a kind of lexical adaptation of cond_timedwai=
t() and family. I personally just mutex locked shared resources in my C cod=
e so I was not aware of this technique.