I think you'll find an interface to the Perl debugger for every decent editor. When I write Perl I normally end up using the Perl debugger at least once and because my editor of choice is Vim I use VimDebug<http://vim.sourceforge.net/scripts/script.php?script_id=663>. VimDebug is an amazing integration to vim that allows you to use the Perl debugger directly or via the source code and allows you to navigate the source as if it were an editing session.
The Perl debugger is useful for all kinds of development; large and small code bases. It is particularly good for debugging a large code base with which you are unfamiliar because you can 'see' how the code works and follow the program flow without having to keep opening and closing files. If your not 100% sure what is going on or have lost track of the current program state you can simply dump out any variable you choose. Out of interest, how do you go about debugging without a debugger? James 2009/4/7 Alex Francis <[email protected]> > On Tue, Apr 7, 2009 at 4:04 PM, max psykx <[email protected]> > wrote: > > I've never written a huge perl project, but when I'm writing perl > > stuff I find it invaluable. IMHO It'd be much better if there was an > > IDE which integrated with it. > > > > Max > > > > Er... like Eclipse, for instance? (With the EPIC plugin) > > http://www.epic-ide.org/index.php > > I've used it too, although I don't have it up and running right now. > > If you try it out, use the "testing" EPIC version, not the "stable" > one - I've found the "testing" one perfectly stable and much better > (can't remember why now, might be performance). > > Alex > _______________________________________________ > BristolBathPM mailing list > [email protected] > http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm >
_______________________________________________ BristolBathPM mailing list [email protected] http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm
