If you're using Windows, I can heartily recommend Open Perl IDE. It hooks in with Perl a treat, and you can even do debugging straight off the code, set watches/breakpoints, etc.
In Linux, my preferred development environment, I tend to just use a basic editor and do things on the command line. I haven't found anything like Open Perl IDE for Linux yet.. although if anyone has any suggestions..
Update: Just went crawling to look for a free Perl IDE for Linux and haven't turned up trumps yet, but I found Perl.com's Resources guide which has a debugging resource section and links to a selection of editors.
| [reply] |
I use vile (a vi look-a-like), with the following Perl specific settings:
define-submode perl shiftwidth 4
1 store-macro
goto-beginning-of-file
append-string "#!/usr/bin/perl\n\n"
append-string "use strict;\n";
append-string "use warnings;\n";
set-mode "perlmode"
position-window b
open-line-below-and-append-chars
~endm
2 store-macro
save-file
shell-command &cat "perl " $cfilname
~endm
3 store-macro
save-file
shell-command &cat "perl -c " $cfilname
~endm
4 store-macro
save-file
shell-command "make"
~endm
bind-key execute-macro-1 ^A-p
bind-key execute-macro-2 ^A-r
bind-key execute-macro-3 ^A-c
bind-key execute-macro-4 ^A-m
Do I need more for development? Well, a second xterm is
useful, and make. I love make. The only
times I've replaced Perl programs that I wrote myself,
with something else I've replaced them with Makefiles.
Lots of fluids are important too. I always have one or more
bottles of carbonated water on my desk, and coke (or other
sodas) and/or tea is usually near as well.
For debugging, I mostly use plain print statements,
sometimes I use YAML to show the structure of a complex
datastructure (I find Data::Dumpers output to be unreadable). Command line options I may use for debugging
are: -c, -Dr and -MO=Deparse.
I've never used the Perl debugger. Sometimes I use
[ps]?trace/truss (or whatever it's called on
the box I'm working on) or snoop/tcpdump for
debugging. Or I peek in the source. And then there are
top, ps, *stat, glance,
/proc/*, netstat, route and
syslog which I use to debug and investigate problems with. Obviously, some of the tools are more Perl
specific than others.
Abigail | [reply] [d/l] [select] |
do you have recommentations about tools to develop perl programs and to debug perl programs
Now I admit I'm a professional linguist, but I understood this question right away. You're looking to see whether we have recommendations for developing and debugging Perl programs, verdad?
I use vim, the Perl Debugger (perl -d), strict, warnings, Data::Dumper, and Diagnostics.
You can use vim and EMACS as IDEs, but some people like Eclipse with the EPIC plugins.
| [reply] |
What do you mean by 'perl tools'? Tools written in Perl?
Tools to develop perl? Tools to develop Perl programs?
Tools to debug perl? Tools to debug Perl programs?
Abigail | [reply] |
I use Eclipse IDE platform with the EPIC Perl editor plug-in on both Windows (XP) and Linux (RH8).
jdtoronto | [reply] |
| [reply] |
i use xemacs cperl-mode
NO MICRO$OFT products please
LINUX por favor!
| [reply] |
The non-Microsoft world is bigger than just Linux.
Abigail
| [reply] |