Just a note, please take their comments about how well-documented their code is with a grain of salt. When I started my position I had assurances that the code was well-documented, well-written, performs well, could easily be ported to mod_perl, had very few bugs, etc., etc. Unfortunately, I have spent the last year and a half rewriting that code (not all at once, of course). It was full of zillions of global variables, some home-grown "template" system which apparently required that *every* function in the entire system take as arguments $xml and returns $xml (some gigantic hashref), so there was NO error checking going on at all ANYWHERE. Half of it used strict, the other half didn't. Every module had copy/pasted dozens of functions of duplicated code. And this guy thought it was all just great (he forgot to tell me when he left the company that he was leaving because management asked for some relatively simple features that were virtually impossible for him to implement, not only because he was a moron but also because the foundation was so bad and the db design was so wrong that it almost required a complete rewrite just to add features which should be trivial). Anyway, I think I just went off on my first tangent here so I'm sorry :)

In reply to Re: General Debugging Tips by saberworks
in thread General Debugging Tips by o2bwise

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.