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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.70.48.38 with SMTP id i6mr7389511pdn.5.1406279489714;
 Fri, 25 Jul 2014 02:11:29 -0700 (PDT)
X-Received: by 10.140.105.200 with SMTP id c66mr238812qgf.4.1406279489663;
 Fri, 25 Jul 2014 02:11:29 -0700 (PDT)
Path: 
 border1.nntp.dca1.giganews.com!nntp.giganews.com!h18no7251359igc.0!news-out.google.com!j6ni12934qas.0!nntp.google.com!v10no2411713qac.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Fri, 25 Jul 2014 02:11:29 -0700 (PDT)
In-Reply-To: <wccppgu9398.fsf@shell01.TheWorld.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=91.55.222.226;
 posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf
NNTP-Posting-Host: 91.55.222.226
References: <50bdb713-7ce1-411b-810b-9bdee1d26b7a@googlegroups.com>
 <cd50cff5-a37a-4c41-a091-cc6c0aae6c8f@googlegroups.com>
 <7581b098-ea30-4b34-a51e-2f0dd5a57563@googlegroups.com>
 <wcciomn3dng.fsf@shell01.TheWorld.com>
 <00aae9b5-42e8-40e8-a2dd-7e56ecd2bca3@googlegroups.com>
 <wccppgu9398.fsf@shell01.TheWorld.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <1cbcaaba-766a-4b4d-a487-ecb77735efb2@googlegroups.com>
Subject: Re: Timeouts in Ada
From: AdaMagica <christ-usch.grein@t-online.de>
Injection-Date: Fri, 25 Jul 2014 09:11:29 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: number.nntp.dca.giganews.com comp.lang.ada:187852
Date: 2014-07-25T02:11:29-07:00
List-Id: <comp.lang.ada>

On Thursday, July 24, 2014 5:37:39 PM UTC+2, Robert A Duff wrote:

> It makes perfect sense to enqueue on multiple entries.
> In fact, "select call_1 or delay..." enqueues twice (once on
> the entry call, and once on the timer queue).

That wasn't my point. I just indicated the model.

> Regarding your analogy: There's a supermarket near me where they have
> just one queue, and the person at the head of the queue takes the first
> available cash point.  In a sense, they're enqueued on multiple cash
> points.  ;-)  Like the multi-way call proposed (and rejected) for Ada 9X,
> they only use one.

That's a very sensible service - I often wish supermarkets here had this model. I find this only in airport counters.

But this is not the same as

>    select
>      call_1(params);
>    or
>      call_2(params);
>    or
>      delay 10;
>    end select;

In your supermarket, there is just one queue, and on the top, you are dispatched to a free cash point, and all of those do the same.

In that multiple select above, the different entries all would/could do different things. In your model: You queue before a gasoline station, a shoemaker, a hardware shop, an accomodation broker; you enter the first free of those.