Help. /me has a hard time parsing that. With Jesse's proposal that would render the second statement useless, as the first already states that you want it the way it is for 5.18. Nothing wrong with that. But in that proposal, you (as a programmer, not as author here) ignore all the stuff that was released after 5.18 so no 5.20; is useless as you already said so.

What I was looking for is about what Corion said. I need at least version X (because an important bug was fixed or some new (at that time) killer feature was being introduced (like Unicode 6.0 in 5.14.1) but I trust perl to have not fucked up in later releases. That is how I always interpreted the use v5.12; syntax.


Enjoy, Have FUN! H.Merijn

In reply to Re^4: Back to the __future__ by Tux
in thread Back to the __future__ by cdarke

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.