really wish you would follow up with at least a brief description of what you consider to be effective use of a debugger
I can't speak for tye, but here's a couple of ways that I occasionally use a debugger.
- Understanding code. If I've been handed a big ball of mud sans tests then the debugger is a handy tool for understanding how the bugger runs. Although these days I tend to use Devel::Cover first to give me an overview of what's going on.
- Exploratory testing. Poking at the code to see if I can make it fail and then go write a failing test. I've not use it myself yet, but Devel::TestEmbed looks like a nice little tool to make this task easier.
-
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.
|
