I used to debug a lot like you do, it works fine. Another
good trick is to abuse Data::Dumper for debugging when
diving into data structures and objects. But these all
can be trememdously slower sometimes, especially if the original
code is not yours. I did not really start using
debuggers until I got to my current job where some of the
programs are 30k lines long, none of which were written
by me. They are not a bad sized programs,
but some were written in the most bizzare way, and no
strict. Yet I still have to fix the bugs that are reported.
It is hard to get into debuggers at first, but
investigate some of the gui ones like Devel::ptkdb or DDD.
Getting really familiar with a good debugger is (in my opinion)
one of the most advantageous things any programmer can do.
-
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.
|