←back to thread

327 points AareyBaba | 3 comments | | HN request time: 0.501s | source
Show context
jandrewrogers ◴[] 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 #
genewitch ◴[] 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 #
GoblinSlayer ◴[] No.46185738[source]
stdio.h is not what you would use in safe code.
replies(1): >>46187404 #
1. fragmede ◴[] No.46187404[source]
do they use f35io.h?
replies(2): >>46187853 #>>46188819 #
2. whaleofatw2022 ◴[] No.46187853[source]
Afair they use a lot of stuff related to the Green Hills toolchain.
3. ecshafer ◴[] No.46188819[source]
Depends. You use vendor specific libraries for hard real time systems, or in house libraries, or roll your own functions.