To me, the debugger is indispensable, and I'd urge everyone to learn and use it.
Besides using "perl -de 1" to test any code snippet, there are many cases where the debugger is much better than print (of course, I print too, and log with Log4Perl). For example, if a script gets an array of files to process, and something is not right for one of the files, it's so easy to run through the debugger and change the array on the fly than to change the code. And when you are handed someone else's code, going through the debugger will reveal much more of the flow than print.
On a side note, I think php doesn't have as nice an interactive shell, it's one of the things I really miss when I do php.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|