News for hackers. Stuff that matters.
Re:Don’t assume that safety comes for free: a Swift case study by mcguire on Tuesday December 06, 2016 @10:49PM (#13120329)
"That’s because I do not think it is universally a good thing that software should crash when an overflow occurs. Think about the software that runs in your brain. Sometimes you experience bugs. For example, an optical illusion is a fault in your vision software. Would you want to fall dead whenever you encounter an optical illusion? That does not sound entirely reasonable, does it? Moreover, would you want this “fall dead” switch to make all of your brain run at half its best speed? In software terms, this means that a mission-critical application could crash because an unimportant function in a secondary routine overflows."

That is a ridiculous analogy. What if we replace "optical illusion" with "hallucination"?

More importantly, what if there were some sort of middle ground between continuing on as if nothing happened on an error and crashing completely?

There are no comments on this comment yet.