Sean Schofield wrote:
Ummm... I guess you guys don't do a lot of debugging then? You would rather imagine what a value was a certain point in time rather then actually know what is was? If you never make mistakes then there is no issue but if you think a value is 'x' it only take 5 seconds to be 100% sure. Of course there is System.out.println but are you going to add those for all 10, 15 values in question?
This is a valid point and debuggers have really come a long way. I still use the logging method personally because I've found debuggers dull my ability to see the bugs early. When I have to look at the code and think about the assumptions I've made I can frequently find and fix the bug before the debugger would have ever fired up.
And then there are those occasional times where the code just behaves different in a debugger, paused under a microscope than it does running wild.
Plus, I type really fast. In the time it takes some programmers to figure out where they want to set their break-points, setup their watches, etc... I've already put my log statements in, recompiled, and started running.
But I have been tempted a few times... I'll admit that. ;) -Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
