Quotes of the week [LWN.net]

Quotes of the week

Posted Jul 14, 2006 19:27 UTC (Fri) by Wummel (subscriber, #7591)
Parent article: Quotes of the week

Good quote from Andrew Morton about error checking. Some programs ignore it, even books about programming strip their examples of error handling code, usually to have less code.

I'd yet like to see a programming book that emphasizes on error checking and gets it right in their examples. Error handling requires tedious and hard work, but as Andrew said in his post, missing error checks result in crashes that are even harder to debug.

(Log in to post comments)

Quotes of the week

Posted Jul 15, 2006 0:51 UTC (Sat) by Tara_Li (subscriber, #26706) [Link]

Once upon a time, code documented what variables were expected to be set going in, what variables were going to be set upon return, and since this was in the era of mostly global variables, what variables would be trashed in between. (Ok, I'll admit this was in BASIC, FORTRAN, and Assembler.) But of course, with the rise of the Object-Oriented paradigm, where you're supposed to be able to put *ANYTHING* into the function, and get something sensible out, this was no longer supposed to make sense to do. All these insane levels of abstraction we've gotten into do is hide the bugs.

Quotes of the week

Posted Jul 20, 2006 12:23 UTC (Thu) by brantgurga (guest, #22667) [Link]

There is one book I have found that either shows good error handling or specifically says that it has been omitted to clarify the example. That book was Writing Secure Code coauthored by Michael Howard from Microsoft Press.