Debugging is not such an odd concept once you realize you are fallible. Nobody is perfect, and debugging is a good humbling and learning experience for us all. I always learn more debugging than when I am coding.

I have friends that get so frustrated when they compile something and get 300 errors. Like they expect their code to be perfect. I would be frustrated if there were no errors, because then I would have to find my errors with out the aid of the compiler.

I dont know, I find my compilers/interpreters extremely forgiving, and actually fairly polite.

$a ='foo'
print $a

syntax error at - line 2, near "print"
[download]

Isnt that cool. Not only is it non judgemental, it tells you where your error is and then even gives you the chance to fix it. I cant think of a better reality. They could be a lot more realistic:

$a = 'foo'
print $a

Error you idiot.  Your code has been deleted, you no longer
have permission to use this compiler, and all the other
computers and programmers on the network have been informed 
of your imcompetence!
[download]

Now that is harsh, sharp and unforgiving.
Debugging, like life, is what you make of it. So enjoy!

---

---

• 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.