Part of my problem is....half the programmers WANT to use strict but can't see a way of implementing it, the other half have never been exposed. Managers would see it as a loss of productivity to devote time solely to getting another development copy going and working to get it cleaned. The management point of view is "It runs, therefore it does not need to be fixed. Fixing something that executes is a loss of productivy, hence forbidden."
All the code will eventually get cycled through naturally over time. I was maybe wishing too much for a solution where as those familiar with strict cycled through the code, they could clean as they modified, upgraded, replaced, etc.
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.