Best error handler
Best error handler
catch {
exec('rm -rf /*')
}
17 comments
-
Back in my days working as .NET developer on Windows 7, I came into work one morning to find a colleague fuming that his machine had died on him.
He spent the whole morning reinstalling Windows and getting his environment set back up, and then pulled the branch he was working on, happy to finally be done with setup and get back to work. Ran his test suite and bam, machine crashes!
It was only at that point the penny dropped. We took a look at his branch, and sure enough he'd accidentally written a test that, when ran, deleted his entire C: drive!
That particular lesson made me very careful when writing any code that does things with the filesystem.
-
Or, you know, run it in a chroot.
-
Hey, if Valve gets to wipe home directories in released software, developers should get the chance to do it in their test code.
-
-
-
I'm a big fan of just leaving the catch block blank as a nice fuck you gesture
-
You'd love vbscript: https://stackoverflow.com/q/2202869
-
-
On Error Resume Next
-
catch {}-
No, no. You're supposed to drop tables, not throw them.
-
If you drop them all the way from the top of the stack, this is what happens
-
-
-
You got the French language initials backwards, OP.
It should be
rm -fr /*-
Also, to make sure there are no linguistic roots left over on your system that it might grow from again, add
--no-preserve-root. -
For real
-
-
Seppuku exception handling is wild
-
Having your filesystem on the line might actually make some people write decent code.
-
Certainly nicer than my SDL experience of
catch { window.becomeunclosable(); }
-
Halt and catch fire
-
The Apple way...
17 comments