←back to thread

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

(www.youtube.com)
327 points AareyBaba | 2 comments | 07 Dec 25 18:07 UTC | HN request time: 0s | source
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 #
Animats ◴[07 Dec 25 23:53 UTC] No.46186673[source]▶
As is common in hard real time code, there is no dynamic allocation during operation:

    allocation/deallocation from/to the free store (heap) 
    shall not occur after initialization.
This works fine when the problem is roughly constant, as it was in, say, 2005. But what do things look like in modern AI-guided drones?
replies(5): >>46186795 #>>46186825 #>>46187422 #>>46188382 #>>46188948 #
1. mrgaro ◴[08 Dec 25 06:10 UTC] No.46188948[source]▶
There are missiles in which the allocation rate is calculated per second and then the hardware just has enough memory for the entire duration of the missile's flight plus a bit more. Garbage collection is then done by exploding the missile on the target ;)
replies(1): >>46192822 #
2. superxpro12 ◴[08 Dec 25 14:48 UTC] No.46192822[source]▶
We call this "explosive deallocation". Destructors have a whole new meaning.