however, I could say with certainty that I must beone of the few who has never used the debugger todebug code
however, I could say with certainty that I must be
one of the few who has never used the debugger to
At a recent job, I found a bug no one knew existed with just one pass through a tool routine with the debugger. It was important because performance was one of their issues, and the tool was taking twice as long as was needed to perform its task. I wasn't looking for a bug in the tool, merely passing through it on the way to finding a bug in a different procedure.
I use the debugger all the time; I use it when I'm not debugging, sometimes just to walk through a process to ensure it works the way I think it works.
Is it possible you spend most of your debugging time looking at code you wrote or code written by people trained by you.
nah, I just take the Progress corporate line : it's not a bug, it's a feature
That way I don't need to debug ...
FWIW, this bizarre behavior I was seeing was eventually tracked down as a bug by Tech Support. I don't know if the fix made it into drop 2, but it was an actual bug ... just very hard to put a box around.
Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice http://www.cintegrity.com
I think I'm on Julian's side on this one. I can't say that I do it, but I don't know that it is insane. Some people like to put their THEN at the end of the IF line, which would tend to make the next line a naked DO. I prefer a THEN DO, myself, but I don't think the other standard is insane.