From: "J-P. Rosen" <rosen@adalog.fr>
Subject: Re: Ravenscar References
Date: Tue, 22 Jan 2019 10:25:08 +0100
Date: 2019-01-22T10:25:08+01:00 [thread overview]
Message-ID: <q26nhh$nr4$1@dont-email.me> (raw)
In-Reply-To: <q25k2g$of1$1@franka.jacob-sparre.dk>
Le 22/01/2019 à 00:19, Randy Brukardt a écrit :
> I don't think it is possible to "convert" regular Ada code into Ravenscar
> (unless, of course, it doesn't use any tasks ;-). You pretty much have to
> completely rewrite it with Ravenscar in mind. (In this way, it is very much
> like using SPARK.)
I don't fully agree with that statement; it all depends where you start
from.
I recently helped one of my clients who wanted to move to Ravenscar. The
original structure was all Ada83, communicating with rendezvous.
However, it was already safety critical, therefore based on cyclic,
never ending tasks, and limited communications. It was reasonably easy
to define patterns for matching the existing structure into Ravenscar
patterns.
--
J-P. Rosen
Adalog
2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX
Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00
http://www.adalog.fr
next prev parent reply other threads:[~2019-01-22 9:25 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
2019-01-20 17:12 ` Jeffrey R. Carter
2019-01-21 23:19 ` Randy Brukardt
2019-01-22 9:25 ` J-P. Rosen [this message]
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