I am looking for a Windows Perl IDE with debugger like Komodo but free.
I have seen Eclipse+EPIC but I don't want to install Eclipse here .
Padre doesn't have debugger built in.
+2
A:
For Emacs there's the Perl Development Environment. Just use -d/Ctrl-c Ctrl-d for the debugger. Emacs runs on Windows, by the way.
Pedro Silva
2009-12-13 08:46:13
A:
Why use an IDE when you can do pretty much everything with the good ol' perl debugger?
Kiffin
2009-12-13 09:27:11
+7
A:
Komodo Edit is free.
Perl already comes with the best debuggers in the world: print and Test::More.
However, people keep asking this question, so we've listed all the ones we know about in perlfaq3.
brian d foy
2009-12-13 11:16:13
Calling `print` a debugging tool is like calling the clapper a "home automation tool." There's really no substitute for being able to stop, look around, and step.
Michael Carman
2009-12-13 15:11:28
@Michael: I call "holy war" (is there a Godwin's law for that?). This is one of those issues that simply divides people. For many programmers, judicious use of `print` is *precisely* a substitute for stopping, looking around and stepping (which they find tedious and annoying).
Telemachus
2009-12-13 15:15:20
@Michael: You forget the other half of what I said: unit tests. Write small, compartmentalized subroutines, have good tests, and use something like Log4perl to turn on debugging output. Maybe you don't like print(), but it's what most good Perl programmers I know use. And indeed, it is a holy war. That's why I gave my opinion, but also pointed to the extensive list of IDEs I maintain in the perlfaq.
brian d foy
2009-12-13 19:02:00
@brian: I'm a big fan of unit testing but I think it's disingenuous to suggest it as a debugging technique. Outside of the ideal situation you describe it's likely to be ineffective (or at least inefficient). The power of a debugger is being able to see *exactly* what the code is doing free of the human bias that selecting what to print and/or test entails. That said, maybe I'm just bitter because I recently had to debug embedded C code via `printf` over a serial port. The edit-compile-load-run-review cycle was maddening; a working debugger would have sped things up tenfold.
Michael Carman
2009-12-13 22:14:25
The situation I describe is how I actually develop, not some ideal situation. If you think that a debugger doesn't introduce bias, you just don't understand how debuggers work. If you want to talk about C, you're in the wrong place.
brian d foy
2009-12-15 06:33:04
+2
A:
There's an early version of a debugger plugin for Padre (check CPAN). I don't think it's ready for prime time, but if you were willing to donate some of your own time to improve it...
tsee
2009-12-13 12:36:34