Whenever I'm debugging a problem, and I have no idea what's going wrong, my first instinct is to say: Print out *all* the variables.
My coworkers used to give me strange looks, and I'd get conversations that went like this:
Me: "Hey, print the value of X"
Them: "I know what it is. It's 3."
Me: "Print it out anyway."
Them: "Fine." Output: 3
Me: "Good. Now print the value of Y..."
Repeat for many, many variables (incidentally, this often became code that logged gobs of data to a file). Eventually, we'd get to a variable where my coworker thought it was one value, and the variable was another value.
"Oh, crap! I see the problem..."
This is especially necessary for languages like C where a runaway pointer or stack overflow can trash a variable from a completely different context.
Fortunately, they're starting to understand my debugging methods now :)
}"for split/</;$_=$,,y[A-Z a-z]
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||