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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Where to find Ravenscar compatible ADT Containers (List, Vector,
 stack)
Date: Tue, 28 Aug 2018 19:24:21 -0500
Organization: JSA Research & Innovation
Message-ID: <pm4p3l$afb$1@franka.jacob-sparre.dk>
References: <eec01618-ee08-4f7e-be3d-cb16ef2beb4b@googlegroups.com>
Injection-Date: Wed, 29 Aug 2018 00:24:22 -0000 (UTC)
Injection-Info: franka.jacob-sparre.dk;
 posting-host="rrsoftware.com:24.196.82.226";
	logging-data="10731"; mail-complaints-to="news@jacob-sparre.dk"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246
Xref: reader02.eternal-september.org comp.lang.ada:54287
Date: 2018-08-28T19:24:21-05:00
List-Id: <comp.lang.ada>

"Daniel Norber" <danielnorberto@gmail.com> wrote in message 
news:eec01618-ee08-4f7e-be3d-cb16ef2beb4b@googlegroups.com...
>
> 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.