← Back to context

Comment by thomashabets2

9 hours ago

Do you know if the code bases are of the kind where dynamic memory (among many other features) is disallowed?

Defense industry can work around that.

  This sparked an interesting memory for me.  I was once working with a customer who was producing on-board software for a missile.  In my analysis of the code, I pointed out that they had a number of problems with storage leaks.  Imagine my surprise when the customers chief software engineer said "Of course it leaks".  He went on to point out that they had calculated the amount of memory the application would leak in the total possible flight time for the missile and then doubled that number.  They added this much additional memory to the hardware to "support" the leaks.  Since the missile will explode when it hits its target or at the end of its flight, the ultimate in garbage collection is performed without programmer intervention.

https://devblogs.microsoft.com/oldnewthing/20180228-00/?p=98...

Some of them, probably.

From the job postings, many of them seem to be physics simulations of various kinds where (in my experience) memory is allocated on the heap without a second thought. Well, there are second thoughts, but those second thoughts are about performance.