Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Being rather new to writing Perl, I'm still learning some new debugging tools, but I have carried one practice over from my other programming languages that has greatly helped - printing the contents of my data structures.

I tend to deal with rather compex data structures fairly often and it has lead me to become almost obsessed with seeing exactly what data I have stored in my structures - especially when I've found a bug. I've noticed that, all too often, fellow programmers simply assume that the data that's in their structures is correct and that their logic is wrong. They then spend countless hours trying to find the faulty logic only to find that their data was no good in the first place.

My debugging rule of thumb is to make sure that you know exactly what you're dealing with and then you can step through your code with a debugger or even by hand, if need be. Without knowing if your data is correct in the first place, there's no way of truly debugging your code. I think this is something that programmers (sometimes very good programmers) take for granted and fail to inspect.

Is that something that other people have noticed? I think that I might just feel this way because I deal with so many complex data structures.

- Sherlock

In reply to Re: Are debugging skills atrophying? by Sherlock
in thread Are debugging skills atrophying? by dws

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chanting in the Monastery: (4)
As of 2024-03-29 15:41 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found