On Fri, 14 Aug 2009 00:52:24 -0400, Chas. Owens wrote: > I have seen the opposite: too many coders sticking with print instead of > picking up a debugger when the situation called for one. I tend to > debug with a combination of looking at the code, logs, and print > statements, but a good visual debugger can be a godsend. The biggest > problem with print statements is that you are modifying the code and you > might inadvertently change something or leave a debug statement in the > code.
Right. Not to mention if you want to follow the execution into code that resides in a system-wide library. The effort involved there in using print () statements is considerably larger than running the debugger. -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/ http://www.informit.com/store/product.aspx?isbn=0137001274 -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
