←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.193s | 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 #
jandrewrogers ◴[08 Dec 25 00:12 UTC] No.46186825[source]▶
Why would the modern environment materially change this? The initialized resource allocation reflects the limitations of the hardware. That budget is what it is.

I can't think of anything about "modern AI-guided drones" that would change the fundamental mechanics. Some systems support very elastic and dynamic workloads under fixed allocation constraints.

replies(1): >>46188200 #
Animats ◴[08 Dec 25 04:10 UTC] No.46188200[source]▶
Basic flight control is a fixed-sized problem. More military aircraft systems now on what the environment and enemy are doing.
replies(2): >>46188281 #>>46189090 #
1. jasonwatkinspdx ◴[08 Dec 25 04:24 UTC] No.46188281[source]▶
You're just imagining things at this point.

The overwhelming majority of embedded systems are desired around a max buffer size and known worst case execution time. Attempting to balance resources dynamically in a fine grained way is almost always a mistake in these systems.

Putting the words "modern" and "drone" in your sentence doesn't change this.