On Fri, Aug 14, 2009 at 09:18, Shawn H. Corey<shawnhco...@gmail.com> wrote: snip > 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. :) snip
Are you using a visual debugger or a commandline debugger? I find this makes all of the difference in the world. Try downloading a trial version of [Komodo IDE][1] or using [ddd][2]. I detest IDEs, but visual debuggers are incredibly more useful than commandline debuggers, and I find most people's aversion to debuggers goes away when they are presented with one. Another very useful tool is the REPL. Take a look at [Carp::REPL][3] and [CGI::Inspect][4] which are like print statements on steroids. [1] : http://www.activestate.com/komodo/ [2] : http://www.gnu.org/software/ddd/ [3] : http://search.cpan.org/dist/Carp-REPL/lib/Carp/REPL.pm [4] : http://search.cpan.org/dist/CGI-Inspect/lib/CGI/Inspect.pm -- 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/
