If requirements don't dictate a version of Perl to target, what version do you target when writing code for reuse?

I generally target 5.6. It is probably the most widely installed perl these days and I have never been in a situation (yet) where I absolutely needed a 5.8 feature. Indeed, I don't know that I've ever absolutely needed a 5.6 feature, but things like lexical filehandles, our instead of use vars, etc. are rather convenient.

Put differently, what features are you willing to give up for backwards compatible code?

I'm not willing to give up much beyond Perl 5.6. IMHO, 5.6 is really the time when Perl 5 became a mature, "stable" programming language. 5.8 is a great accomplishment but it's not as big a milestone was 5.6 was.

In reply to Re: Writing for backwards compatibility by friedo
in thread Writing for backwards compatibility by xdg

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!
  • 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:
    & &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.