Re: Ravenscar - program termination

Sorry, but I don't see anything in the concept of high-integrity
software that would make it a norm. High-integrity software is a set of
quality objectives, whereas infinite loops are (or aren't) part of
system requirements. These should stay independent, even though I
understand that expectations for both often come in pairs.

The Ravenscar profile is aimed to high-integrity real-time systems. A
static set of working tasks
is a requirement to perform sound feasibility analysis (at least
within a given execution mode).

Still, it looks like I cannot say:

pragma Profile(Ravenscar);

in my Hello World program even though this program meets the objectives
of the profile. That's not fair! :-)

On real-time kernels supporting the Ravenscar profile, even the main
procedure must contain an infinite loop.

Regards,

M.B.

.