cFE

The JPL C rules are quite old, but avoiding dynamic allocation outside initialization is am considered best practice for spaceflight software regardless of language. Here's the recommendation from NASA's language-agnostic cFS: 4.2.4 Consolidate Resource Allocations It is generally recommended to consolidate resource allocations to the application initialization function(s). Allocations and setup of resources such as memory pools and child tasks should happen once during initialization in order to provide more determinism during run time. From: https://github.com/nasa/cFE/blob/main/docs/cFE%20Application... The ESA Ada standard also recommends all allocation occur at initialization, and requires exceptions to be justified.

If people want to look at some Real Deal Space Code, here's some parts I like: CoreFlight System's executive code: https://github.com/nasa/cFE/tree/main/modules/es/fsw/src Any code from the core of RTEMS: https://gitlab.rtems.org/rtems/rtos/rtems/-/tree/main/cpukit... The code isn't special but it is neat and tidy, and very very clear. It says what it does, and it does something small and does it well.

Coding standards can be a pain, but most rules make sense and if they don't make your code difficult to read and unwieldy you should probably create an exception. One example where such an exception would have been justified is found in cFE: https://github.com/nasa/cFE/blob/04c0cc342415575f855dc00960a... Thousands of lines of clutter in the unit tests because they are not using a function-like macro.