Please note that good programmers disagree with each other on how valuable debuggers are. In the thread starting at
Are debuggers good? you will find discussion of both points of view.
In this case the most obvious problem is the fact that the subroutine is 200 lines long. While I don't like to say that there are absolute rules in programming, whenever the section of code that you are working with does not all fit on your screen at once, bug counts skyrocket. Furthermore a 200 line subroutine has a lot of behaviour encapsulated in a form where you cannot easily work through and fix each function, again a bad thing.
The usual rule of thumb is that 50 lines should be the maximum function length. The average that I quote for myself is about 10 lines.
I would far prefer to point a person in that direction than tell them to debug in a way that I personally don't.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.