On Fri, Aug 14, 2009 at 00:21, Uri Guttman<u...@stemsystems.com> wrote: snip > i started with punch cards. print was all you had besides thorough and > deep analysis of your code. that is a talent lost on too many coders > today. and even today proper use of print is better than any debug > tool. but it is still a skill to learn, where and what to print and how > to analyze the results. i have seen many good coders not get that and > they stick with debuggers. i find the simplicity of print and my total > control of what gets printed, etc better than learning more commands, > having to repeat a set of debug commands (yes, you can macro and preset > them but that is still more work), etc. print is always there in any > programs (and debuggers have issues with complex sets of processes, and > daemons and such). snip
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. -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read. -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
