←back to thread

The C++ standard for the F-35 Fighter Jet [video]

(www.youtube.com)
327 points AareyBaba | 6 comments | 07 Dec 25 18:07 UTC | HN request time: 0s | source | bottom
Show context
jandrewrogers ◴[07 Dec 25 18:35 UTC] No.46183899[source]▶
For those interested, the F-35 (née Joint Strike Fighter) C++ coding standards can be found here, all 142 pages of it:

https://www.stroustrup.com/JSF-AV-rules.pdf

replies(8): >>46184308 #>>46184351 #>>46184419 #>>46184493 #>>46184536 #>>46184570 #>>46185099 #>>46186673 #
1. genewitch ◴[07 Dec 25 20:57 UTC] No.46185099[source]▶
In general, are these good recommendations for building software for embedded or lower-spec devices? I don't know how to do preprocessor macros anyhow, for instance - so as i am reading this i am like "yeah, i agree..." until the no stdio.h!
replies(2): >>46185738 #>>46187935 #
2. GoblinSlayer ◴[07 Dec 25 22:10 UTC] No.46185738[source]▶
stdio.h is not what you would use in safe code.
replies(1): >>46187404 #
3. fragmede ◴[08 Dec 25 01:49 UTC] No.46187404[source]▶
do they use f35io.h?
replies(2): >>46187853 #>>46188819 #
4. whaleofatw2022 ◴[08 Dec 25 03:04 UTC] No.46187853{3}[source]▶
Afair they use a lot of stuff related to the Green Hills toolchain.
5. dmoy ◴[08 Dec 25 03:23 UTC] No.46187935[source]▶
Embedded more so than just lower-spec devices. Depends on the domain too.

stdio.h is fine in some embedded contexts, and very very not fine in others

6. ecshafer ◴[08 Dec 25 05:48 UTC] No.46188819{3}[source]▶
Depends. You use vendor specific libraries for hard real time systems, or in house libraries, or roll your own functions.