more on how to specify C<configure_requires> when creating a distribution
for CPAN.
-=head2 C<each> is now more flexible
+=head2 C<each>, C<keys>, C<values> are now more flexible
-The C<each> function can now operate on arrays.
+The C<each>, C<keys>, C<values> function can now operate on arrays.
=head2 C<when> as a statement modifier
=head2 REGEXPs are now first class
-Internally, Perl now treates compiled regular expressions (such as
+Internally, Perl now treats compiled regular expressions (such as
those created with C<qr//>) as first class entities. Perl modules which
serialize, deserialize or otherwise have deep interaction with Perl's
internal data structures need to be updated for this change. Most
=item *
Perl's command-line switch "-P", which was deprecated in version 5.10.0, has
-now been removed.
+now been removed. The CPAN module C<< Filter::cpp >> can be used as an
+alternative.
=back
core versions of these modules warnings will issue a deprecation warning.
If you ship a packaged version of Perl, either alone or as part of a
-larger system, then you should carefully consider the reprecussions of
+larger system, then you should carefully consider the repercussions of
core module deprecations. You may want to consider shipping your default
build of Perl with packages for some or all deprecated modules which
install into C<vendor> or C<site> perl library directories. This will
Perl's developers have fixed several problems with the recognition of
C<\N{...}> constructs. As part of this, perl will store any scalar
or regex containing C<\N{I<name>}> or C<\N{U+I<wide hex char>}> in its
-definition in UTF-8 format. (This was true previously for all occurences
+definition in UTF-8 format. (This was true previously for all occurrences
of C<\N{I<name>}> that did not use a custom translator, but now it's
always true.)
https://perl5.git.perl.org / perl5.git / blobdiff