DO-178b safety-critical C++

[Robin Rowe]

Can anyone tell me what work has been done to standardize C++ for
safety-critical systems?

What C++ features are considered unsafe for DO-178b? For example, with
flight software, any program termination will result in destruction of
the spacecraft. Since an uncaught exception would be catastrophic, is
banning using exceptions here the best course?

Robin

[daniele...@gmail.com]

Some standards were developed with C++ guidelines and feature limitations.
The most important are:

- MISRA C++
- JSF Air Vehicle C++ Coding Standard

Tipically features like dynamic memory allocation are forbidden, automatic conversions are restricted and so on.

[daniele...@gmail.com]

The JSF C++ Coding Standard forbids also Exceptions.

Il giorno venerdì 26 febbraio 2016 07:45:22 UTC+1, Robin Rowe ha scritto:

[Arash Partow]

DO-178B levels C/D are pretty much standard coding nothing special.
Levels A and B have much more stricter requirements - to the point
where I don't think you can use C++ in Level A.

Unless there's a toolchain provider out there that has a Level A
certified c++ toolchain, standard library et al, don't even think
Green Hills has one, so there's really no point...

[Robert Ramey]

On 2/25/16 10:45 PM, Robin Rowe wrote:
> Can anyone tell me what work has been done to standardize C++ for
> safety-critical systems?
>

Note that next Tuesday, the C++ standards committee SG-6 will consider
the proposal safe integers which is specifically designed for these
types of applications. Feel free to read the proposal and comment on
this list.


https://isocpp.org/blog/2016/02/2016-02-pre-jacksonville-mailing-available

http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0228r0.pdf

Robert Ramey