As far as debuggers go, I used them extensively for a number of years when I was working on multi-threaded C code, but I haven't touched them since I moved to Perl. This is probably due to the quicker turnaround time of making changes in perl (e.g. to insert a debugging print statement, or a Data::Dumper of a structure) and the fact that perl doesn't tend to have really pernicious low-level problems like C (e.g. core dumps, memory leaks, etc). Debuggers are nice when you have exausted other paths and you have time to burn. For me, it's not worth the effort to pick a good GUI for this.
As far as IDE's, I use emacs. If you pick something that is relatively generic that has syntax highlighting and some intellegent editing (e.g. vim), you won't have to learn a new environment when the next new language you are required to use comes down the pike, though Perl is a welcome relief...
bluto
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.