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 2002:a02:4ddc:: with SMTP id
 t89-v6mr3696661jad.19.1535588513054;
        Wed, 29 Aug 2018 17:21:53 -0700 (PDT)
X-Received: by 2002:aca:d551:: with SMTP id m78-v6mr2547oig.1.1535588512946;
 Wed, 29 Aug 2018 17:21:52 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!w19-v6no101536itb.0!news-out.google.com!z5-v6ni5ite.0!nntp.google.com!g24-v6no101045iti.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Wed, 29 Aug 2018 17:21:52 -0700 (PDT)
In-Reply-To: <pm4p3l$afb$1@franka.jacob-sparre.dk>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=173.71.213.10;
 posting-account=QF6XPQoAAABce2NyPxxDAaKdAkN6RgAf
NNTP-Posting-Host: 173.71.213.10
References: <eec01618-ee08-4f7e-be3d-cb16ef2beb4b@googlegroups.com>
 <pm4p3l$afb$1@franka.jacob-sparre.dk>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <69e04c61-8ea3-40e2-bb9d-e5a128247df3@googlegroups.com>
Subject: Re: Where to find Ravenscar compatible ADT Containers (List, Vector,
 stack)
From: Jere <jhb.chat@gmail.com>
Injection-Date: Thu, 30 Aug 2018 00:21:53 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader02.eternal-september.org comp.lang.ada:54293
Date: 2018-08-29T17:21:52-07:00
List-Id: <comp.lang.ada>

On Tuesday, August 28, 2018 at 8:24:23 PM UTC-4, Randy Brukardt wrote:
> "Daniel Norber" wrote in message 
> >
> > The standard ADA.Containers library is not prepared for Ravenscar use.
> > Even bounded versions, like Bounded_double_Linked_List have several 
> > violations
> >of Ravenscar, like Implicit_Heap_Allocation when i try to instantiate it, 
> >and bind it.
> 
> The bounded versions aren't supposed to have any heap allocation, see for 
> instance A.18.19(16/3). I'd expect that to be a requirement for a compiler 
> supporting Ravenscar.
> 
> The other versions aren't intended to be used in safety-critical 
> environments where heap use has to be constrained.
> 
> I'd suggest that this is a compiler bug that ought to be reported to your 
> vendor. (And Simon suggests that it might have been an old bug already fixed 
> in the current versions.)
> 
>                                             Randy.

I have a question about this as it has always bothered me.  The
section that specifies that is under Implementation Advice, which
doesn't sound binding.  That sounds more like it is a suggestion
to the vendor rather than a requirement.  Is Implementation
Advice such that a conforming Ada compiler must follow it
(so not really advice at that point)?  I've intentionally avoided
bounded containers in situations where I want portability for
some of my embedded targets that don't use heap because it 
doesn't sound guaranteed that it will not use heap, even
if my current compiler implements it that way now.