Shlomi Fish wrote:
My recent impression of most Perl programmers has been the opposite - most of
them have been too lazy or unmotivated to learn about the perl -d flag (or
similar interactive debuggers), and are always using print's or going on IRC
asking "What is wrong with this code?" I find the perl debugger an
indispensable tool and am actively using it.
While print's have their rightful place, I still think the perl debugger is
too under-used.
"We will encourage you to develop the three great virtues of a
programmer: laziness, impatience, and hubris." -- Larry Wall
from http://www.c2.com/cgi/wiki?LazinessImpatienceHubris
The last time I used a debugger was on a large C project. For small
programs and unit testing, it was fine, but when things went over 2000
lines, it became increasingly frustrating to use. Of course, print
statements have their limits too but it happens at about 5000 lines.
I use Data::Dumper a lot, so most of my debugging statements have
"Dumper" in them, making them easy to find. For those that don't, I add
"# TEMPORARY" at the end. And I leave them behind; I just put a "#" in
front of them. :)
--
Just my 0.00000002 million dollars worth,
Shawn
Programming is as much about organization and communication
as it is about coding.
I like Perl; it's the only language where you can bless your
thingy.
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
