←back to thread

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

(www.youtube.com)
327 points AareyBaba | 1 comments | 07 Dec 25 18:07 UTC | HN request time: 0.195s | 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. m4nu3l ◴[08 Dec 25 01:52 UTC] No.46187422[source]▶
What you are actually doing here is moving allocation logic from the heap allocator to your program logic.

In this way you can use pools or buffers of which you know exactly the size. But, unless your program is always using exactly the same amount of memory at all times, you now have to manage memory allocations in your pool/buffers.