You In Here :
/
/
proc /
self /
root /
usr /
share /
perl5 /
pod /=encoding utf8
=head1 NAME
perl5120delta - what is new for perl v5.12.0
=head1 DESCRIPTION
This document describes differences between the 5.10.0 release and the
5.12.0 release.
Many of the bug fixes in 5.12.0 are already included in the 5.10.1
maintenance release.
You can see the list of those changes in the 5.10.1 release notes
(L
).
=head1 Core Enhancements
=head2 New C syntax
This new syntax allows a module author to set the $VERSION of a namespace
when the namespace is declared with 'package'. It eliminates the need
for C and similar constructs. E.g.
package Foo::Bar 1.23;
# $Foo::Bar::VERSION == 1.23
There are several advantages to this:
=over
=item *
C<$VERSION> is parsed in exactly the same way as C
=item *
C<$VERSION> is set at compile time
=item *
C<$VERSION> is a version object that provides proper overloading of
comparison operators so comparing C<$VERSION> to decimal (1.23) or
dotted-decimal (v1.2.3) version numbers works correctly.
=item *
Eliminates C<$VERSION = ...> and C clutter
=item *
As it requires VERSION to be a numeric literal or v-string
literal, it can be statically parsed by toolchain modules
without C the way MM-Eparse_version does for C<$VERSION = ...>
=back
It does not break old code with only C, but code that uses
C will need to be restricted to perl 5.12.0 or newer
This is analogous to the change to C from two-args to three-args.
Users requiring the latest Perl will benefit, and perhaps after several
years, it will become a standard practice.
However, C requires a new, 'strict' version
number format. See L<"Version number formats"> for details.
=head2 The C<...> operator
A new operator, C<...>, nicknamed the Yada Yada operator, has been added.
It is intended to mark placeholder code that is not yet implemented.
See L.
=head2 Implicit strictures
Using the C syntax with a version number greater or equal
to 5.11.0 will lexically enable strictures just like C
would do (in addition to enabling features.) The following:
use 5.12.0;
means:
use strict;
use feature ':5.12';
=head2 Unicode improvements
Perl 5.12 comes with Unicode 5.2, the latest version available to
us at the time of release. This version of Unicode was released in
October 2009. See L for
further details about what's changed in this version of the standard.
See L for instructions on installing and using other versions
of Unicode.
Additionally, Perl's developers have significantly improved Perl's Unicode
implementation. For full details, see L below.
=head2 Y2038 compliance
Perl's core time-related functions are now Y2038 compliant. (It may not mean much to you, but your kids will love it!)
=head2 qr overloading
It is now possible to overload the C.
=head2 Pluggable keywords
Extension modules can now cleanly hook into the Perl parser to define
new kinds of keyword-headed expression and compound statement. The
syntax following the keyword is defined entirely by the extension. This
allow a completely non-Perl sublanguage to be parsed inline, with the
correct ops cleanly generated.
See L for the mechanism. The Perl core
source distribution also includes a new module
L, which implements reverse Polish notation
arithmetic via pluggable keywords. This module is mainly used for test
purposes, and is not normally installed, but also serves as an example
of how to use the new mechanism.
Perl's developers consider this feature to be experimental. We may remove
it or change it in a backwards-incompatible way in Perl 5.14.
=head2 APIs for more internals
The lowest layers of the lexer and parts of the pad system now have C
APIs available to XS extensions. These are necessary to support proper
use of pluggable keywords, but have other uses too. The new APIs are
experimental, and only cover a small proportion of what would be
necessary to take full advantage of the core's facilities in these
areas. It is intended that the Perl 5.13 development cycle will see the
addition of a full range of clean, supported interfaces.
Perl's developers consider this feature to be experimental. We may remove
it or change it in a backwards-incompatible way in Perl 5.14.
=head2 Overridable function lookup
Where an extension module hooks the creation of rv2cv ops to modify the
subroutine lookup process, this now works correctly for bareword
subroutine calls. This means that prototypes on subroutines referenced
this way will be processed correctly. (Previously bareword subroutine
names were initially looked up, for parsing purposes, by an unhookable
mechanism, so extensions could only properly influence subroutine names
that appeared with an C<&> sigil.)
=head2 A proper interface for pluggable Method Resolution Orders
As of Perl 5.12.0 there is a new interface for plugging and using method
resolution orders other than the default linear depth first search.
The C3 method resolution order added in 5.10.0 has been re-implemented as
a plugin, without changing its Perl-space interface. See L for
more information.
=head2 C<\N> experimental regex escape
Perl now supports C<\N>, a new regex escape which you can think of as
the inverse of C<\n>. It will match any character that is not a newline,
independently from the presence or absence of the single line match
modifier C. It is not usable within a character class. C<\N{3}>
means to match 3 non-newlines; C<\N{5,}> means to match at least 5.
C<\N{NAME}> still means the character or sequence named C, but
C no longer can be things like C<3>, or C<5,>.
This will break a L which allows numbers for character names, as C<\N{3}> will
now mean to match 3 non-newline characters, and not the character whose
name is C<3>. (No name defined by the Unicode standard is a number,
so only custom translators might be affected.)
Perl's developers are somewhat concerned about possible user confusion
with the existing C<\N{...}> construct which matches characters by their
Unicode name. Consequently, this feature is experimental. We may remove
it or change it in a backwards-incompatible way in Perl 5.14.
=head2 DTrace support
Perl now has some support for DTrace. See "DTrace support" in F.
=head2 Support for C in CPAN module metadata
Both C and C now support the C
keyword in the F metadata file included in most recent CPAN
distributions. This allows distribution authors to specify configuration
prerequisites that must be installed before running F
or F.
See the documentation for C or C for
more on how to specify C when creating a distribution
for CPAN.
=head2 C, C, C are now more flexible
The C, C, C function can now operate on arrays.
=head2 C as a statement modifier
C is now allowed to be used as a statement modifier.
=head2 C<$,> flexibility
The variable C<$,> may now be tied.
=head2 // in when clauses
// now behaves like || in when clauses
=head2 Enabling warnings from your shell environment
You can now set C<-W> from the C environment variable
=head2 C
C now allows you to locally delete a hash entry.
=head2 New support for Abstract namespace sockets
Abstract namespace sockets are Linux-specific socket type that live in
AF_UNIX family, slightly abusing it to be able to use arbitrary
character arrays as addresses: They start with nul byte and are not
terminated by nul byte, but with the length passed to the socket()
system call.
=head2 32-bit limit on substr arguments removed
The 32-bit limit on C arguments has now been removed. The full
range of the system's signed and unsigned integers is now available for
the C and C arguments.
=head1 Potentially Incompatible Changes
=head2 Deprecations warn by default
Over the years, Perl's developers have deprecated a number of language
features for a variety of reasons. Perl now defaults to issuing a
warning if a deprecated language feature is used. Many of the deprecations
Perl now warns you about have been deprecated for many years. You can
find a list of what was deprecated in a given release of Perl in the
C file for that release.
To disable this feature in a given lexical scope, you should use C For information about which language features
are deprecated and explanations of various deprecation warnings, please
see L. See L below for the list of features
and modules Perl's developers have deprecated as part of this release.
=head2 Version number formats
Acceptable version number formats have been formalized into "strict" and
"lax" rules. C takes a strict version number.
C and the L object constructors take lax
version numbers. Providing an invalid version will result in a fatal
error. The version argument in C is first parsed as a
numeric literal or v-string and then passed to C
(and must then pass the "lax" format test).
These formats are documented fully in the L module. To a first
approximation, a "strict" version number is a positive decimal number
(integer or decimal-fraction) without exponentiation or else a
dotted-decimal v-string with a leading 'v' character and at least three
components. A "lax" version number allows v-strings with fewer than
three components or without a leading 'v'. Under "lax" rules, both
decimal and dotted-decimal versions may have a trailing "alpha"
component separated by an underscore character after a fractional or
dotted-decimal component.
The L module adds C and C
functions to check a scalar against these rules.
=head2 @INC reorganization
In C<@INC>, C and C now occur after after the current
version's C and C. Modules installed into
C and C will now be loaded in preference to
those installed in C and C.
=head2 REGEXPs are now first class
Internally, Perl now treats compiled regular expressions (such as
those created with C/C switch statement handles complex statements better
than Perl 5.10.0 did (These enhancements are also available in
5.10.1 and subsequent 5.10 releases.) There are two new cases where
C now interprets its argument as a boolean, instead of an
expression to be used in a smart match:
=over
=item flip-flop operators
The C<..> and C<...> flip-flop operators are now evaluated in boolean
context, following their usual semantics; see L.
Note that, as in perl 5.10.0, C will not work to test
whether a given value is an integer between 1 and 10; you should use
C instead (note the array reference).
However, contrary to 5.10.0, evaluating the flip-flop operators in
boolean context ensures it can now be useful in a C, notably
for implementing bistable conditions, like in:
when (/^=begin/ .. /^=end/) {
# do something
}
=item defined-or operator
A compound expression involving the defined-or operator, as in
C, will be treated as boolean if the first
expression is boolean. (This just extends the existing rule that applies
to the regular or operator, as in C.)
=back
=head2 Smart match changes
Since Perl 5.10.0, Perl's developers have made a number of changes to
the smart match operator. These, of course, also alter the behaviour
of the switch statements where smart matching is implicitly used.
These changes were also made for the 5.10.1 release, and will remain in
subsequent 5.10 releases.
=head3 Changes to type-based dispatch
The smart match operator C<~~> is no longer commutative. The behaviour of
a smart match now depends primarily on the type of its right hand
argument. Moreover, its semantics have been adjusted for greater
consistency or usefulness in several cases. While the general backwards
compatibility is maintained, several changes must be noted:
=over 4
=item *
Code references with an empty prototype are no longer treated specially.
They are passed an argument like the other code references (even if they
choose to ignore it).
=item *
C<%hash ~~ sub {}> and C<@array ~~ sub {}> now test that the subroutine
returns a true value for each key of the hash (or element of the
array), instead of passing the whole hash or array as a reference to
the subroutine.
=item *
Due to the commutativity breakage, code references are no longer
treated specially when appearing on the left of the C<~~> operator,
but like any vulgar scalar.
=item *
C is always false (since C can't be a key in a
hash). No implicit conversion to C<""> is done (as was the case in perl
5.10.0).
=item *
C<$scalar ~~ @array> now always distributes the smart match across the
elements of the array. It's true if one element in @array verifies
C<$scalar ~~ $element>. This is a generalization of the old behaviour
that tested whether the array contained the scalar.
=back
The full dispatch table for the smart match operator is given in
L.
=head3 Smart match and overloading
According to the rule of dispatch based on the rightmost argument type,
when an object overloading C<~~> appears on the right side of the
operator, the overload routine will always be called (with a 3rd argument
set to a true value, see L.) However, when the object will
appear on the left, the overload routine will be called only when the
rightmost argument is a simple scalar. This way, distributivity of smart
match across arrays is not broken, as well as the other behaviours with
complex types (coderefs, hashes, regexes). Thus, writers of overloading
routines for smart match mostly need to worry only with comparing
against a scalar, and possibly with stringification overloading; the
other common cases will be automatically handled consistently.
C<~~> will now refuse to work on objects that do not overload it (in order
to avoid relying on the object's underlying structure). (However, if the
object overloads the stringification or the numification operators, and
if overload fallback is active, it will be used instead, as usual.)
=head2 Other potentially incompatible changes
=over 4
=item *
The definitions of a number of Unicode properties have changed to match
those of the current Unicode standard. These are listed above under
L. This change may break code that expects the old
definitions.
=item *
The boolkeys op has moved to the group of hash ops. This breaks binary
compatibility.
=item *
Filehandles are now always blessed into C.
The previous behaviour was to bless Filehandles into L
(an empty proxy class) if it was loaded into memory and otherwise
to bless them into C.
=item *
The semantics of C have changed slightly.
See L<"Modules and Pragmata"> for more information.
=item *
Perl's developers now use git, rather than Perforce. This should be
a purely internal change only relevant to people actively working on
the core. However, you may see minor difference in perl as a consequence
of the change. For example in some of details of the output of C. See L for more information.
=item *
As part of the C 2.x to 3.x upgrade, the experimental
C module has been removed.
See L for more details.
=item *
As part of the C upgrade, the
C and C modules
have been removed from this distribution.
=item *
C no longer contains the C<%:patchlevel> hash.
=item *
C now returns undef.
=item *
Unsupported private C API functions are now declared "static" to prevent
leakage to Perl's public API.
=item *
To support the bootstrapping process, F no longer builds with
UTF-8 support in the regexp engine.
This allows a build to complete with PERL_UNICODE set and a UTF-8 locale.
Without this there's a bootstrapping problem, as miniperl can't load
the UTF-8 components of the regexp engine, because they're not yet built.
=item *
F's @INC is now restricted to just C<-I...>, the split of
C<$ENV{PERL5LIB}>, and "C<.>"
=item *
A space or a newline is now required after a C<"#line XXX"> directive.
=item *
Tied filehandles now have an additional method EOF which provides the
EOF type.
=item *
To better match all other flow control statements, C may no
longer be used as an attribute.
=item *
Perl's command-line switch "-P", which was deprecated in version 5.10.0, has
now been removed. The CPAN module C<< Filter::cpp >> can be used as an
alternative.
=back
=head1 Deprecations
From time to time, Perl's developers find it necessary to deprecate
features or modules we've previously shipped as part of the core
distribution. We are well aware of the pain and frustration that a
backwards-incompatible change to Perl can cause for developers building
or maintaining software in Perl. You can be sure that when we deprecate
a functionality or syntax, it isn't a choice we make lightly. Sometimes,
we choose to deprecate functionality or syntax because it was found to
be poorly designed or implemented. Sometimes, this is because they're
holding back other features or causing performance problems. Sometimes,
the reasons are more complex. Wherever possible, we try to keep deprecated
functionality available to developers in its previous form for at least
one major release. So long as a deprecated feature isn't actively
disrupting our ability to maintain and extend Perl, we'll try to leave
it in place as long as possible.
The following items are now deprecated:
=over
=item suidperl
C is no longer part of Perl. It used to provide a mechanism to
emulate setuid permission bits on systems that don't support it properly.
=item Use of C<:=> to mean an empty attribute list
An accident of Perl's parser meant that these constructions were all
equivalent:
my $pi := 4;
my $pi : = 4;
my $pi : = 4;
with the C<:> being treated as the start of an attribute list, which
ends before the C<=>. As whitespace is not significant here, all are
parsed as an empty attribute list, hence all the above are equivalent
to, and better written as
my $pi = 4;
because no attribute processing is done for an empty list.
As is, this meant that C<:=> cannot be used as a new token, without
silently changing the meaning of existing code. Hence that particular
form is now deprecated, and will become a syntax error. If it is
absolutely necessary to have empty attribute lists (for example,
because of a code generator) then avoid the warning by adding a space
before the C<=>.
=item C<< UNIVERSAL->import() >>
The method C<< UNIVERSAL->import() >> is now deprecated. Attempting to
pass import arguments to a C statement will result in a
deprecation warning.
=item Use of "goto" to jump into a construct
Using C to jump from an outer scope into an inner scope is now
deprecated. This rare use case was causing problems in the
implementation of scopes.
=item Custom character names in \N{name} that don't look like names
In C<\N{I}>, I can be just about anything. The standard
Unicode names have a very limited domain, but a custom name translator
could create names that are, for example, made up entirely of punctuation
symbols. It is now deprecated to make names that don't begin with an
alphabetic character, and aren't alphanumeric or contain other than
a very few other characters, namely spaces, dashes, parentheses
and colons. Because of the added meaning of C<\N> (See L
experimental regex escape>), names that look like curly brace -enclosed
quantifiers won't work. For example, C<\N{3,4}> now means to match 3 to
4 non-newlines; before a custom name C<3,4> could have been created.
=item Deprecated Modules
The following modules will be removed from the core distribution in a
future release, and should be installed from CPAN instead. Distributions
on CPAN which require these should add them to their prerequisites. The
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 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 or C perl library directories. This will
inhibit the deprecation warnings.
Alternatively, you may want to consider patching F
to provide deprecation warnings specific to your packaging system
or distribution of Perl, consistent with how your packaging system
or distribution manages a staged transition from a release where the
installation of a single package provides the given functionality, to
a later release where the system administrator needs to know to install
multiple packages to get that same functionality.
You can silence these deprecation warnings by installing the modules
in question from CPAN. To install the latest version of all of them,
just install C.
=over
=item L
=item L
=item L
=item L
Switch is buggy and should be avoided. You may find Perl's new
C/C feature a suitable replacement. See L for more information.
=back
=item Assignment to $[
=item Use of the attribute :locked on subroutines
=item Use of "locked" with the attributes pragma
=item Use of "unique" with the attributes pragma
=item Perl_pmflag
C is no longer part of Perl's public API. Calling it now
generates a deprecation warning, and it will be removed in a future
release. Although listed as part of the API, it was never documented,
and only ever used in F, and prior to 5.10, F. In
core, it has been replaced by a static function.
=item Numerous Perl 4-era libraries
F, F, F, F, F,
F, F, F, F, F,
F, F, F, F,
F, F, F, F, F,
F, F, F, F, F,
F, F, F, F, and
F are all now deprecated. Earlier, Perl's developers
intended to remove these libraries from Perl's core for the 5.14.0 release.
During final testing before the release of 5.12.0, several developers
discovered current production code using these ancient libraries, some
inside the Perl core itself. Accordingly, the pumpking granted them
a stay of execution. They will begin to warn about their deprecation
in the 5.14.0 release and will be removed in the 5.16.0 release.
=back
=head1 Unicode overhaul
Perl's developers have made a concerted effort to update Perl to be in
sync with the latest Unicode standard. Changes for this include:
Perl can now handle every Unicode character property. New documentation,
L, lists all available non-Unihan character properties. By
default, perl does not expose Unihan, deprecated or Unicode-internal
properties. See below for more details on these; there is also a section
in the pod listing them, and explaining why they are not exposed.
Perl now fully supports the Unicode compound-style of using C<=>
and C<:> in writing regular expressions: C<\p{property=value}> and
C<\p{property:value}> (both of which mean the same thing).
Perl now fully supports the Unicode loose matching rules for text between
the braces in C<\p{...}> constructs. In addition, Perl allows underscores
between digits of numbers.
Perl now accepts all the Unicode-defined synonyms for properties and
property values.
C. (See
L> sequence.
=item *
C<\X> will now match a sequence which includes the C and C
characters.
=item *
C<\X> will now always match at least one character, including an initial
mark. Marks generally come after a base character, but it is possible in
Unicode to have them in isolation, and C<\X> will now handle that case,
for example at the beginning of a line, or after a C. And this is
the part where C<\X> doesn't match the things that it used to that don't
make sense. Formerly, for example, you could have the nonsensical case
of an accented LF.
=item *
C<\X> will now match a (Korean) Hangul syllable sequence, and the Thai
and Lao exception cases.
=back
Otherwise, this change should be transparent for the non-affected
languages.
C<\p{...}> matches using the Canonical_Combining_Class property were
completely broken in previous releases of Perl. They should now work
correctly.
Before Perl 5.12, the Unicode C property
and a Perl extension had the same name, which led to neither matching
all the correct values (with more than 100 mistakes in one, and several
thousand in the other). The Perl extension has now been renamed to be
C (short: C). It has the
same meaning as was previously intended, namely the union of all the
non-canonical Decomposition types, with Unicode C being just
one of those.
C<\p{Decomposition_Type=Canonical}> now includes the Hangul syllables.
C<\p{Uppercase}> and C<\p{Lowercase}> now work as the Unicode standard
says they should. This means they each match a few more characters than
they used to.
C<\p{Cntrl}> now matches the same characters as C<\p{Control}>. This
means it no longer will match Private Use (gc=co), Surrogates (gc=cs),
nor Format (gc=cf) code points. The Format code points represent the
biggest possible problem. All but 36 of them are either officially
deprecated or strongly discouraged from being used. Of those 36, likely
the most widely used are the soft hyphen (U+00AD), and BOM, ZWSP, ZWNJ,
WJ, and similar characters, plus bidirectional controls.
C<\p{Alpha}> now matches the same characters as C<\p{Alphabetic}>. Before
5.12, Perl's definition definition included a number of things that aren't
really alpha (all marks) while omitting many that were. The definitions
of C<\p{Alnum}> and C<\p{Word}> depend on Alpha's definition and have
changed accordingly.
C<\p{Word}> no longer incorrectly matches non-word characters such
as fractions.
C<\p{Print}> no longer matches the line control characters: Tab, LF,
CR, FF, VT, and NEL. This brings it in line with standards and the
documentation.
C<\p{XDigit}> now matches the same characters as C<\p{Hex_Digit}>. This
means that in addition to the characters it currently matches,
C<[A-Fa-f0-9]>, it will also match the 22 fullwidth equivalents, for
example U+FF10: FULLWIDTH DIGIT ZERO.
The Numeric type property has been extended to include the Unihan
characters.
There is a new Perl extension, the 'Present_In', or simply 'In',
property. This is an extension of the Unicode Age property, but
C<\p{In=5.0}> matches any code point whose usage has been determined
I Unicode version 5.0. The C<\p{Age=5.0}> only matches code points
added in I version 5.0.
A number of properties now have the correct values for unassigned
code points. The affected properties are Bidi_Class, East_Asian_Width,
Joining_Type, Decomposition_Type, Hangul_Syllable_Type, Numeric_Type,
and Line_Break.
The Default_Ignorable_Code_Point, ID_Continue, and ID_Start properties
are now up to date with current Unicode definitions.
Earlier versions of Perl erroneously exposed certain properties that
are supposed to be Unicode internal-only. Use of these in regular
expressions will now generate, if enabled, a deprecation warning message.
The properties are: Other_Alphabetic, Other_Default_Ignorable_Code_Point,
Other_Grapheme_Extend, Other_ID_Continue, Other_ID_Start, Other_Lowercase,
Other_Math, and Other_Uppercase.
It is now possible to change which Unicode properties Perl understands
on a per-installation basis. As mentioned above, certain properties
are turned off by default. These include all the Unihan properties
(which should be accessible via the CPAN module Unicode::Unihan) and any
deprecated or Unicode internal-only property that Perl has never exposed.
The generated files in the C directory are now more
clearly marked as being stable, directly usable by applications. New hash
entries in them give the format of the normal entries, which allows for
easier machine parsing. Perl can generate files in this directory for
any property, though most are suppressed. You can find instructions
for changing which are written in L.
=head1 Modules and Pragmata
=head2 New Modules and Pragmata
=over 4
=item C
C is a new lexically-scoped alternative for the C module.
The bundled version is 2.06_01. Note that in this release, using a string
eval when C is in effect can cause the autodie behaviour to leak
into the surrounding scope. See L for more details.
Version 2.06_01 has been added to the Perl core.
=item C
Version 2.024 has been added to the Perl core.
=item C
C allows you to lexically disable or enable overloading
for some or all operations.
Version 0.001 has been added to the Perl core.
=item C
C establishes an ISA relationship with base classes at compile
time. It provides the key feature of C
Version 1.40 has been added to the Perl core.
=item C
Version 1.03 has been added to the Perl core.
=item C
Version 2.4 has been added to the Perl core.
=item C
Version 0.003 has been added to the Perl core.
=back
=head2 Updated Pragmata
=over 4
=item C
Upgraded from version 0.22 to 0.23.
=item C
C now contains the Unicode F database file.
This has the effect of adding some extra C<\N> character names that
formerly wouldn't have been recognised; for example, C<"\N{LATIN CAPITAL
LETTER GHA}">.
Upgraded from version 1.06 to 1.07.
=item C
Upgraded from version 1.13 to 1.20.
=item C
C now supports %.0f formatting internally.
C no longer suppresses C warnings. [perl #71204]
Upgraded from version 1.17 to 1.19.
=item C
In C, the meaning of the C<:5.10> and C<:5.10.X> feature
bundles has changed slightly. The last component, if any (i.e. C) is
simply ignored. This is predicated on the assumption that new features
will not, in general, be added to maintenance releases. So C<:5.10>
and C<:5.10.X> have identical effect. This is a change to the behaviour
documented for 5.10.0.
C now includes the C feature:
use feature "unicode_strings";
This pragma turns on Unicode semantics for the case-changing operations
(C, C, C, C) on strings that don't have the
internal UTF-8 flag set, but that contain single-byte characters between
128 and 255.
Upgraded from version 1.11 to 1.16.
=item C
C now includes the C method to allow subclasses of
C to pick where in %^H to store their stash.
Upgraded from version 0.02 to 0.03.
=item C
Upgraded from version 0.5565 to 0.62.
=item C
C is now implemented as an XS extension. The documented interface has
not changed. Code relying on the implementation detail that some C
methods happened to be available at all times gets to "keep both pieces".
Upgraded from version 1.00 to 1.02.
=item C
C now allow overloading of 'qr'.
Upgraded from version 1.06 to 1.10.
=item C
Upgraded from version 1.67 to 1.75.
=item C
Upgraded from version 1.14 to 1.32.
=item C
C now has support for L as described
earlier in this document and in its own documentation.
Upgraded from version 0.74 to 0.82.
=item C
C has a new C function. It also
includes a new C warning category. See also L for this change.
Upgraded from version 1.06 to 1.09.
=back
=head2 Updated Modules
=over 4
=item C
Upgraded from version 0.24 to 0.38.
=item C
Upgraded from version 1.38 to 1.54.
=item C
Upgraded from version 0.79 to 0.87.
=item C
Upgraded from version 5.63 to 5.70.
=item C
Upgraded from version 0.74 to 0.78.
=item C
Upgraded from version 1.05 to 1.12.
=item C
Upgraded from version 0.83 to 0.96.
=item C
Upgraded from version 1.09 to 1.11_01.
=item C
Upgraded from version 3.29 to 3.48.
=item C
Upgraded from version 0.33 to 0.36.
NOTE: C is deprecated and may be removed from a future
version of Perl.
=item C
Upgraded from version 2.008 to 2.024.
=item C
Upgraded from version 1.9205 to 1.94_56.
=item C
Upgraded from version 0.84 to 0.90.
=item C
Upgraded from version 0.06_02 to 0.46.
=item C
Upgraded from version 2.121_14 to 2.125.
=item C
Upgraded from version 1.816_1 to 1.820.
=item C
Upgraded from version 3.13 to 3.19.
=item C
Upgraded from version 1.15 to 1.16.
=item C
Upgraded from version 2.36_01 to 2.39.
=item C
Upgraded from version 5.45 to 5.47.
=item C
Upgraded from version 2.23 to 2.39.
=item C
Upgraded from version 5.62 to 5.64_01.
=item C
Upgraded from version 0.21 to 0.27.
=item C
Upgraded from version 1.13 to 1.16.
=item C
Upgraded from version 0.2 to 0.22.
=item C
Upgraded from version 1.44 to 1.55.
=item C
Upgraded from version 6.42 to 6.56.
=item C
Upgraded from version 1.51_01 to 1.57.
=item C
Upgraded from version 2.18_02 to 2.21.
=item C
Upgraded from version 0.14 to 0.24.
=item C
Upgraded from version 2.04 to 2.08_01.
=item C
Upgraded from version 0.18 to 0.22.
=item C
Upgraded from version 0.82 to 0.84.
=item C
Upgraded from version 1.07 to 1.08.
=item C
Upgraded from version 2.37 to 2.38.
=item C
Upgraded from version 1.23_01 to 1.25_02.
=item C
Upgraded from version 1.07 to 1.10.
=item C
Upgraded from version 0.40_1 to 0.54.
=item C
Upgraded from version 1.05 to 2.01.
=item C
Upgraded from version 1.12 to 1.14.
=item C
Upgraded from version 0.18 to 0.21.
=item C
Upgraded from version 0.01 to 0.02.
=item C