This is really evil... But the title is right - if you were debugging with printf in the first place, then this is better. It doesn't mean it's good in any way. The better way to make printf-debugging obsolete is:
- catch exceptions where they might occur and log as much information as possible
- use tests before publishing the code
- use something like log4X so you can actually log what's happening at the level you need
- do not ever think "Assuming that /usr/share/dict/words is sufficient" - you were wrong at "Assuming"
- catch exceptions where they might occur and log as much information as possible
- use tests before publishing the code
- use something like log4X so you can actually log what's happening at the level you need
- do not ever think "Assuming that /usr/share/dict/words is sufficient" - you were wrong at "Assuming"