←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: 0.387s | source
Show context
mwkaufma ◴[07 Dec 25 18:15 UTC] No.46183728[source]▶
TL;DR

- no exceptions

- no recursion

- no malloc()/free() in the inner-loop

replies(9): >>46183820 #>>46183900 #>>46184073 #>>46184113 #>>46184198 #>>46184398 #>>46184472 #>>46184588 #>>46185500 #
krashidov ◴[07 Dec 25 19:36 UTC] No.46184398[source]▶
Has anyone else here banned exceptions (for the most part) in less critical settings (like a web app)?

I feel like that's the way to go since you don't obscure control flow. I have also been considered adding assertions like TigerBeetle does

https://github.com/tigerbeetle/tigerbeetle/blob/main/docs/TI...

replies(3): >>46184593 #>>46185874 #>>46185984 #
1. mwkaufma ◴[07 Dec 25 19:58 UTC] No.46184593[source]▶
Lots of games, and notably the Unreal Engine, compile without exceptions. EASTL back in the day was in part written to avoid the poor no-exception support in Dinkumware STL and STLport.
replies(1): >>46186856 #
2. jesse__ ◴[08 Dec 25 00:16 UTC] No.46186856[source]▶
Basically all high profile engine teams I know of ban exceptions. They're worse than useless