The generally recommended practice now is to use $VERSION =~ tr/_//d;

A much better idea, IMO.
And, if I ever release another devel version of a module, that's what I'll use.

Cheers,
Rob

PS
I haven't been releasing devel versions for a while now.
Apparently, not all smokers test devel releases, and it was not uncommon for me to have the devel version pass everywhere, only to fail on some other smoker as soon as it became a stable release.
I couldn't see the point in that. Instead, I choose to do broad based testing locally and then do a stable release.

In reply to Re^8: Why eval $version? by syphilis
in thread Why eval $version? by Aldebaran

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.