FatDog,
As some of the replies indicate, this is a terribly hard problem to solve with an automatic one-size-fits-all approach. Since you are doing cleanup, it is unlikely that the code has an extensive test suite. If that were the case, it would be possible through trial and error to comment out each module and see if the comprehensive test suite still passed.
Depending on the size and the complexity of the code and the amount of time your boss is willing to let you spend refactoring, you might just want to start from scratch with each one in turn. Examine the code of the prior code, write tests, write code, check tests, bugfix as necessary, document - wash-rinse-repeat.
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.