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.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,25642dc8f94534f6
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nntp.club.cc.cmu.edu!feeder.erje.net!news.musoftware.de!wum.musoftware.de!news.weisnix.org!newsfeed.ision.net!newsfeed2.easynews.net!ision!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Basic question about select
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: <Xns9D68C41D38649fdnbgui7uhu5h8hrnuio@188.40.43.213>
 <1p2m3s7y70lsa$.79fl3we9edva$.dlg@40tude.net>
 <hra886$nku$1@tornado.tornevall.net>
 <li4owy33qsdk$.1h1n04y4qjtme.dlg@40tude.net>
 <hralgc$7ld$1@tornado.tornevall.net>
Date: Thu, 29 Apr 2010 09:37:13 +0200
Message-ID: <8iwpphfe21rz.1oxc0484ag5f1$.dlg@40tude.net>
NNTP-Posting-Date: 29 Apr 2010 09:37:13 CEST
NNTP-Posting-Host: 88fd16a4.newsspool3.arcor-online.net
X-Trace: 
 DXC=[=ZdGZ\S5dE78PK[oJ2ng@McF=Q^Z^V3H4Fo<]lROoRA8kF<OcfhCOKa]LNHib7JTK[6LHn;2LCVN7enW;^6ZC`DIXm65S@:3>OjC1KjkjJdXN
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:11250
Date: 2010-04-29T09:37:13+02:00
List-Id: <comp.lang.ada>

On Wed, 28 Apr 2010 17:47:02 -0700, Jeffrey R. Carter wrote:

> Dmitry A. Kazakov wrote:
>> 
>> If abort to happen after *completion* of the rendezvous then the above
>> shall not deadlock. (I checked this under GNAT/Windows, it deadlocks
>> there.)
> 
> Under Linux/GNAT-gcc 4.3, this deadlocks as given, but does not if a "delay 
> 1.0;" is included in the task before the accept.

You are right.

Much implementation burden just in order to achieve a race condition!

Luckily ATC is a no-no in my coding standard anyway.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de