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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,3e11ef4efc073f6b X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!postnews.google.com!g1g2000pra.googlegroups.com!not-for-mail From: christoph.grein@eurocopter.com Newsgroups: comp.lang.ada Subject: Re: requeue with abort and timed call Date: Mon, 29 Dec 2008 03:17:32 -0800 (PST) Organization: http://groups.google.com Message-ID: <64b95078-2931-40b6-b4f5-6a014d2123e1@g1g2000pra.googlegroups.com> References: <2a60b044-6a5c-4ce6-93e6-6eeefc8806c3@l33g2000pri.googlegroups.com> <1f6rcb1qwt7vx.1mckzyk9ucohf.dlg@40tude.net> <84c56781-1cb1-4d86-be14-e66fc9fdade6@w1g2000prk.googlegroups.com> <4c7abc6f-d6d3-4265-8311-1bbb40cc0c0a@z27g2000prd.googlegroups.com> <94gmm8tk6t6c$.1ngnma4ovauei.dlg@40tude.net> NNTP-Posting-Host: 91.13.232.7 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1230549452 23061 127.0.0.1 (29 Dec 2008 11:17:32 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 29 Dec 2008 11:17:32 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: g1g2000pra.googlegroups.com; posting-host=91.13.232.7; posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5,gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:3109 Date: 2008-12-29T03:17:32-08:00 List-Id: On 29 Dez., 11:55, "Dmitry A. Kazakov" wrote: > My understanding is that for the observer (the caller) servicing is > semantically an atomic operation which ends with the last rendzevous or > protected action. It is not abortable during a rendezvous or a protected > action, but between them it well is (unless it was requeued without abort). But this is exactly what I meant to say. Time line is like following; 0.0 The call of Original_Call *1.0 The expiration time of original call, so no abort, because in rendezvous 3.0 Complete Original_Call *3.0 Queued on Requeued_Call, which is never serviced, but which is also not abortable (no delay active). So I do not see a problem with the behavious as shown in the OP's example. *3.0 Queued on Requeued_Call - hm, you think the delay is still active? We need a language lawyer to enlighten us. GNAT's behaviour follows my interpretation (I experimented a bit with increasing the delays). Is this a bug and I am wrong (may well be)?