How Not to Program in C++
by Thomas Powell on May.14, 2007, under now reading
How Not to Program in C++: 111 Broken Programs and 3 Working Ones, or Why Does 2 + 2 = 5986
I expected many great things from this book. I got mixed results. I usually enjoy figuring out “Bugs of the Day” and the like, but this was book was largely a mix of grading papers from an introductory programming class and debugging buggy programs at work.
Low points:
- Debugging printf format specifiers and forward slash for escaping characters.
- A few fairly long programs with somewhat trivial errors.
High points:
- Bugs encountered as a result of optimizing compilers.
- Exploring of lesser used features of the C/C++ language
- Some interesting puzzles to find where initialization and/or destruction order went wrong.
No comments for this entry yet...
