Re: Ravenscar References

[lyttlec <lyttlec@removegmail.com>]

I think my situation is similar to yours. The project already had to
meet "life safety" for the 1990s. The architectural changes won't be
trivial, but also won't be overwhelming.
To keep from having to re-invent the wheel for lots of common structures
and components. "Free" isn't a requirement, even though the budget is
limited.
On 1/22/19 5:05 PM, Randy Brukardt wrote:
> "J-P. Rosen" <rosen@adalog.fr> wrote in message 
> news:q26nhh$nr4$1@dont-email.me...
>> 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.
> 
> The OP was looking for free resources to do this job for any existing Ada 
> code, and that clearly doesn't exist, and it can't exist. I certainly 
> believe that it can be done if the code is already quite limited and if you 
> hire a Ravenscar expert to help. :-)
> 
>                                     Randy.
> 
>