5.8.8 due to vendor library, currently moving to 5.14 along with vendor upgrade. A vendor supporting only a single version of Perl makes upgrades fun, as a change to the vendor back end can necessitate updating front-end code as well.

A platform change is requiring validation (and an excuse to remedy some past coding sins) of all code anyway, so the ability to bring everything up to the most current infrastructure that the vendor supports in one swell foop is a plus.

Now if I could just get the vendor to support more than one version of Perl at a time so that I can break future updates into a single moving part at a time.

--MidLifeXis


In reply to Re: Roll Call - How new is your Perl? by MidLifeXis
in thread Roll Call - How new is your Perl? by Tommy

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!
  • 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, 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
  • Outside of code tags, you may need to use entities for some characters:
            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.