News for hackers. Stuff that matters.
Re:How to add a million bugs to a program, and why you might... by GauntletWizard on Thursday July 07, 2016 @07:11PM (#12052681)
I toyed with this idea a little while back; I wrote some very critical tooling in bash, and wanted to make certain that no matter where in the program I encountered an error, the second try would work (presuming I had diagnosed the error).

My thought was: These scripts are running with set -euxo pipefail. I can insert a 'false' line between any two lines, run the script, then remove it and run it again and I should still get the correct results. I never finished writing this test tool, but I still think it's a good idea I want to get back to.

There are no comments on this comment yet.