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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,bdf72b2364b0da13
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Received: by 10.68.75.170 with SMTP id d10mr6564078pbw.6.1323798955062;
        Tue, 13 Dec 2011 09:55:55 -0800 (PST)
Path: 
 lh20ni18532pbb.0!nntp.google.com!news1.google.com!postnews.google.com!r6g2000yqr.googlegroups.com!not-for-mail
From: Ada BRL <ada.brl.2011@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Interrupts handling in ADA
Date: Tue, 13 Dec 2011 09:55:54 -0800 (PST)
Organization: http://groups.google.com
Message-ID: <515d5501-c89b-4a9d-82b6-ec3539a0c2cf@r6g2000yqr.googlegroups.com>
References: <30143086.6.1323549838421.JavaMail.geo-discussion-forums@vbbfq24>
 <m2ty589i5g.fsf@pushface.org>
 <6df577eb-9c6a-4f82-95e4-817f6ad1ba6e@r6g2000yqr.googlegroups.com>
 <m2hb14a4t9.fsf@pushface.org> <m2d3bsa3jk.fsf@pushface.org>
NNTP-Posting-Host: 86.169.132.157
Mime-Version: 1.0
X-Trace: posting.google.com 1323798954 16766 127.0.0.1 (13 Dec 2011 17:55:54
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 13 Dec 2011 17:55:54 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: r6g2000yqr.googlegroups.com; posting-host=86.169.132.157;
 posting-account=yig7mwoAAAAAcduNbH7Dpal1sjCSAijA
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: HNKUARELSC
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2
 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2,gzip(gfe)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2011-12-13T09:55:54-08:00
List-Id: <comp.lang.ada>

On 13 Dic, 15:34, Simon Wright <si...@pushface.org> wrote:
> Simon Wright <si...@pushface.org> writes:
> > Also, this isn't called an accept statement; it's an entry call. The wa=
y
> > a task indicates it's prepared to accept an entry call is by an accept
> > statement; protected objects are different. So if instead of Queue bein=
g
> > protected it was a task (not something I'd recommend) the corresponding
> > body part would have looked like
>
> > =A0 =A0accept Get (M : out Message) when not Buffer.Is_Empty do
>
> :blush: I can't believe I said that!
>
> The relevant section of the ARM is 9.7.1, Selective Accept, and it'd
> have looked like
>
> =A0 =A0select
> =A0 =A0 =A0 when not Buffer.Is_Empty =3D>
> =A0 =A0 =A0 =A0 =A0accept Get (M : out Message) do
> =A0 =A0 =A0 =A0 =A0 =A0 M :=3D ...
> =A0 =A0 =A0 =A0 =A0end Get;
> =A0 =A0 =A0 or
> =A0 =A0 =A0 =A0 =A0accept Put ...

Does this means that if the Buffer is empty I will accept the Put
instead of Get? So the "or" refers to the condition before "=3D>"