so far, so good with perl 5.008_001. however, i'm just beginning to use it.

of note: one of my favorite changes, the deprecation of v-strings, may affect your code. from the pod:

=head2 Version Strings (v-strings) Are Deprecated Version Strings (v-strings) have been deprecated. They will not be available after Perl 5.8. The marginal benefits of v-strings were greatly outweighed by the potential for Surprise and Confusion.

for those who use 5.8.0; in scripts (which was never truly portable anyway,) instead of use 5.008;, you'll likely have to make changes.

there are a few other good changes that you may like to read about: the perl debugger has been documented, and bugs have been expunged. also, s/perl -MCPAN/cpan/. and there are even more core and core module tests!

~Particle *accelerates*


In reply to Re: 5.8.1 RC1: good, bad, or ugly? by particle
in thread 5.8.1 RC1: good, bad, or ugly? by RMGir

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.