Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
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

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 or How to display code and escape characters are good places to start.
Log In?

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

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (3)
As of 2021-11-29 06:24 GMT
Find Nodes?
    Voting Booth?

    No recent polls found