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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||