eternal_july

Well, an obvious question to ask is if you are honestly prepared that it is your or your relatives' lives, that are lost in the name of progress / long term gain?

Perhaps, it is easier to speak of things like "short term life lost vs long term life's saved", as long as it is other people losing lives.

"There is no cannibalism in the British navy, absolutely none, and when I say none, I mean there _is_ a certain amount."

To reinforce the sibling comment's point: A very common pattern is when a const variable resides in non-writable memory (happens all the time in embedded), - if you attempt to write to it, you trigger a fault.

So if you cast away constness to conform to some API and then read the value, everything is fine (aside from questionable API design, of course). Modifying the value is another story, though.

> I'm sure we all know what happens when your ISR quietly does a new while some other part of your code is holding one of the locks deep in malloc.

Yeah, what happens is that such code does not pass code review :)

In 99.99% of cases an ISR should only set some flag, that is then checked by code, running in user mode (or whatever it is called for your platform). Then the real work is done in user mode. The remaining 0.01% of cases does not involve using dynamic memory either.

Of course everything doesn't have to be a file (it is only that way on Unices). On Linux everything is a filesystem!

I was semi-hoping, that "résumé validation" would validate it against things like expected buzzword frequency, HR stopwords and so on. The important things, you know.