If your code base now runs on perl 5.8 only, eventually you will have to upgrade. At some point in the future you'll have new hardware on which the legacy OS that come with legacy perl won't boot anymore, so it's not a question whether you upgrade, but when.
With that in mind, advice of the form "Upgrade to at least perl 5.12 because it fixes your $problem" is actually quite valuable, because it gives you reason not delay the upgrade any longer.
Also the more incentive you have to upgrade, the easier it becomes to convince your manager that now would be a good time to spend your resources on upgrading to a newer version of perl. And a list of issues that would be much easier to fix with a newer version of perl is exactly the kind of incentive that convinces managers.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||