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,a4db0fc323f0b09e X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!ecngs!feeder2.ecngs.de!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!news.belwue.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Barrier re-evaluation issue with GNAT 4.3.2 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: Date: Mon, 28 Sep 2009 20:51:26 +0200 Message-ID: <149j9gmsas1fp$.1d62gknnx87q4$.dlg@40tude.net> NNTP-Posting-Date: 28 Sep 2009 20:51:25 CEST NNTP-Posting-Host: fa4f2c0e.newsspool1.arcor-online.net X-Trace: DXC=bS68OLah6bL@Y=h<_c3PkHic==]BZ:afN4Fo<]lROoRA^YC2XCjHcbI]jH`jQQno`ODNcfSJ;bb[EIRnRBaCdWF X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:8518 Date: 2009-09-28T20:51:25+02:00 List-Id: On Mon, 28 Sep 2009 11:38:18 -0700, Jeffrey R. Carter wrote: > An entry call is always potentially blocking, regardless of its barrier; see ARM > 9.5.1. Technically, this code contains a bounded error. Since the potentially > blocking operation was detected, your program should raise Program_Error; GNAT > pretends that it hasn't detected that the operation is potentially blocking and > lets you get away with only a warning. Other compilers (and even other versions > of GNAT) may actually raise Program_Error. A small addition to above. If you wanted to call to an entry from inside a protected procedure you have two options: 1. the callee is made a protected procedure (can be factored out); 2. the caller is made an entry, and the call replaced with requeue. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de