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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,d495ab2e69ad1962 X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!bcklog2.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail NNTP-Posting-Date: Thu, 06 Sep 2007 20:38:02 -0500 From: "Steve" Newsgroups: comp.lang.ada References: <1188914005.607732.277400@57g2000hsv.googlegroups.com> <1188977891.197536.21660@r29g2000hsg.googlegroups.com> Subject: Re: Ravenscar-compliant bounded buffer Date: Thu, 6 Sep 2007 18:38:03 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-RFC2646: Format=Flowed; Original Message-ID: X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 24.20.111.206 X-Trace: sv3-u99HPplsLHLAjXKR1zsJGVuF1Hk20OZhtqU83BS4QhJRA9DK48Ay/qwfM/5TI7Bw7NJ8A1yv2pscTVw!w2vlimJrsc5bO3wNweqPZ7JDurxK6GQNTePLqU1ecmivW7MRbniZfih1VZUn5rKvOz+YmBwTSbDl!um50blgGee+02fYjJKs2KHEtwAVUZw== X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.35 Xref: g2news2.google.com comp.lang.ada:1796 Date: 2007-09-06T18:38:03-07:00 List-Id: "Robert A Duff" wrote in message news:wccps0vkhvo.fsf@shell01.TheWorld.com... > "Steve" writes: > >> Given the restriction, I found your example easy to follow. I don't know >> where to find the Ravenscar document for comparison. > > The Ravenscar profile is documented in section D.13.1 of the latest Ada > Reference Manual. > Unless I'm looking the wrong place, section D.13.1 of the ARM (on AdaIC) just lists the restrictions. The original post was asking about the clarity of an example in a specific document. >> Ada 83 was restrictive in ways that were found to be overly restrictive >> for >> practical application. Some of these retrictions were relaxed with Ada >> 95. >> Perhaps the next round of Ravenscar will do the same. > > I don't see any need to relax Ravenscar, because if you want to use > features not allowed by Ravenscar, you don't have to restrict yourself > to Ravenscar. It's a free choice. I suppose we could argue about > whether the exact set of restrictions is appropriate, but the whole > point is to be restrictive, so the run-time system can be simplified (as > compared to a run-time system that supports full Ada). The choice of the exact set of restrictions that are appropriate is what may in practice make sense to change. After some experience with the restrictions it may be found that a minor modification to one of the restrictions may reduce complexity of implementations. Regards, Steve > > - Bob