From: lyttlec <lyttlec@removegmail.com>
Subject: Re: Ravenscar References
Date: Fri, 18 Jan 2019 14:18:10 -0500
Date: 2019-01-18T14:18:10-05:00 [thread overview]
Message-ID: <q1t8ph$fc0$1@gioia.aioe.org> (raw)
In-Reply-To: lyo98gh3ko.fsf@pushface.org
On 1/16/19 1:15 PM, Simon Wright wrote:
> lyttlec <lyttlec@removegmail.com> writes:
>
>> Can anyone suggest a good reference on using the ravenscar profile? In
>> the Ada books I have, it only gets a one or two page mention. A
>> reference with an extended case study would be great.
>
> You might find something useful at http://cubesatlab.org -
> e.g. http://www.cubesatlab.org:430/PUBLIC/brandon-chapin-HILT-2016.pdf
>
Thanks all for the links. They are a help.
However, I'm looking for something along the lines of porting legacy
code to be ravenscar "safe".
As an illustration, consider making Dmitry A Kazakov's code meet
Ravenscar. I need to port lots of existing more or less standard
components to meet Ravenscar. This is to satisfy some regulatory
authorities.
next prev parent reply other threads:[~2019-01-18 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 17:48 Ravenscar References lyttlec
2019-01-16 18:15 ` Simon Wright
2019-01-18 19:18 ` lyttlec [this message]
2019-01-20 17:12 ` Jeffrey R. Carter
2019-01-21 23:19 ` Randy Brukardt
2019-01-22 9:25 ` J-P. Rosen
2019-01-22 22:05 ` Randy Brukardt
2019-01-28 0:38 ` lyttlec
2019-01-17 5:31 ` J-P. Rosen
2019-01-17 8:46 ` Niklas Holsti
2019-01-29 1:08 ` Jorge Real
2019-01-29 19:24 ` Niklas Holsti
2019-02-01 10:06 ` Jorge Real
2019-02-02 2:13 ` Jere
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox