With this release, Perl is adopting a model that any unsigned value can
be treated as a code point and encoded internally (as utf8) without
-warnings -- not just the code points that are legal in Unicode.
+warnings - not just the code points that are legal in Unicode.
However, unless utf8 warnings have been
explicitly lexically turned off, outputting or performing a
Unicode-defined operation (such as upper-casing) on such a code point
open my $fh, ">", $file;
$fh->autoflush(1); # IO::File not loaded
+=head3 IPv6 support
+
+The C<Socket> module provides new affordances for IPv6,
+including implementations of the C<Socket::getaddrinfo()> and
+C<Socket::getnameinfo()> functions, along with related constants, and a
+handful of new functions. See L<Socket>.
+
=head3 DTrace probes now include package name
The DTrace probes now include an additional argument (C<arg3>) which contains
=head2 New C APIs
-See L</Internal Changes>.
+=head3 CLONE_PARAMS structure added to ease correct thread creation
+
+Modules that create threads should now create C<CLONE_PARAMS> structures
+by calling the new function C<Perl_clone_params_new()>, and free them with
+C<Perl_clone_params_del()>. This will ensure compatibility with any future
+changes to the internals of the C<CLONE_PARAMS> structure layout, and that
+it is correctly allocated and initialised.
+
+=head3 API function to parse statements
+
+The C<parse_fullstmt> function has been added to allow parsing of a single
+complete Perl statement. See L<perlapi> for details.
+
+=head3 API functions for accessing the runtime hinthash
+
+A new C API for introspecting the hinthash C<%^H> at runtime has been added.
+See C<cop_hints_2hv>, C<cop_hints_fetchpvn>, C<cop_hints_fetchpvs>,
+C<cop_hints_fetchsv>, and C<hv_copy_hints_hv> in L<perlapi> for details.
+
+=head3 C interface to C<caller()>
+
+The C<caller_cx> function has been added as an XSUB-writer's equivalent of
+C<caller()>. See L<perlapi> for details.
+
+=head3 Custom per-subroutine check hooks
+
+XS code in an extension module can now annotate a subroutine (whether
+implemented in XS or in Perl) so that nominated XS code will be called
+at compile time (specifically as part of op checking) to change the op
+tree of that subroutine. The compile-time check function (supplied by
+the extension module) can implement argument processing that can't be
+expressed as a prototype, generate customised compile-time warnings,
+perform constant folding for a pure function, inline a subroutine
+consisting of sufficiently simple ops, replace the whole call with a
+custom op, and so on. This was previously all possible by hooking the
+C<entersub> op checker, but the new mechanism makes it easy to tie the
+hook to a specific subroutine. See L<perlapi/cv_set_call_checker>.
+
+To help in writing custom check hooks, several subtasks within standard
+C<entersub> op checking have been separated out and exposed in the API.
+
+=head3 Improved support for custom OPs
+
+Custom ops can now be registered with the new C<custom_op_register> C
+function and the C<XOP> structure. This will make it easier to add new
+properties of custom ops in the future. Two new properties have been added
+already, C<xop_class> and C<xop_peep>.
+
+C<xop_class> is one of the OA_*OP constants, and allows L<B> and other
+introspection mechanisms to work with custom ops that aren't BASEOPs.
+C<xop_peep> is a pointer to a function that will be called for ops of this
+type from C<Perl_rpeep>.
+
+See L<perlguts/Custom Operators> and L<perlapi/Custom Operators> for more
+detail.
+
+The old C<PL_custom_op_names>/C<PL_custom_op_descs> interface is still
+supported but discouraged.
+
+=head3 Return value of C<delete $+{...}>
+
+Custom regular expression engines can now determine the return value of
+C<delete> on an entry of C<%+> or C<%->.
+
+XXX Mention the actual API.
=head1 Security
=head1 Incompatible Changes
-=head2 "C<\cI<X>>"
+Perl 5.14.0 is not binary-compatible with any previous stable release.
+
+=head2 Regular Expressions and String Escapes
+
+=head3 C<\cI<X>>
The backslash-c construct was designed as a way of specifying
non-printable characters, but there were no restrictions (on ASCII
platforms) on what the character following the C<c> could be. Now, that
character must be one of the ASCII characters.
-=head2 Localised tied hashes and arrays are no longed tied
+=head3 \400-\777
+
+Use of C<\400>-C<\777> in regexes in certain circumstances has given
+different, anomalous behavior than their use in all other
+double-quote-like contexts. Since 5.10.1, a deprecated warning message
+has been raised when this happens. Now, all double-quote-like contexts
+have the same behavior, namely to be equivalent to C<\x{100}> -
+C<\x{1FF}>, with no deprecation warning. Use of these values in the
+command line option C<"-0"> retains the current meaning to slurp input
+files whole; previously, this was documented only for C<"-0777">. It is
+recommended, however, because of various ambiguities, to use the new
+C<\o{...}> construct to represent characters in octal.
+
+=head3 Most C<\p{}> properties are now immune to case-insensitive matching
+
+For most Unicode properties, it doesn't make sense to have them match
+differently under C</i> case-insensitive matching than not. And doing
+so leads to unexpected results and potential security holes. For
+example
+
+ m/\p{ASCII_Hex_Digit}+/i
+
+could previously match non-ASCII characters because of the Unicode
+matching rules. There were a number of bugs in this feature until an
+earlier release in the 5.13 series. Now this release reverts, and
+removes the feature completely except for the few properties where
+people have come to expect it, namely the ones where casing is an
+integral part of their functionality, such as C<m/\p{Uppercase}/i> and
+C<m/\p{Lowercase}/i>, both of which match the exact same code points,
+namely those matched by C<m/\p{Cased}/i>. Details are in
+L<perlrecharclass/Unicode Properties>.
+
+XXX The mention of ‘until an earlier release in the 5.13 series’ needs to
+change, but I do not fully understand what happened here.
+
+User-defined property handlers that need to match differently under
+C</i> must change to read the new boolean parameter passed to it which is
+non-zero if case-insensitive matching is in effect or 0 otherwise. See
+L<perluniprops/User-Defined Character Properties>.
+
+=head3 \p{} implies Unicode semantics
+
+Now, a Unicode property match specified in the pattern will indicate
+that the pattern is meant for matching according to Unicode rules, the way
+C<\x{}> does.
+
+=head3 Regular expressions retain their localeness when interpolated
+
+Regular expressions compiled under C<"use locale"> now retain this when
+interpolated into a new regular expression compiled outside a
+C<"use locale">, and vice-versa.
+
+Previously, a regular expression interpolated into another one inherited
+the localeness of the surrounding one, losing whatever state it
+originally had. This is considered a bug fix, but may trip up code that
+has come to rely on the incorrect behavior.
+
+=head3 Stringification of regexes has changed
+
+Default regular expression modifiers are now notated by using
+C<(?^...)>. Code relying on the old stringification will fail. The
+purpose of this is so that when new modifiers are added, such code will
+not have to change (after this one time), as the stringification will
+automatically incorporate the new modifiers.
+
+Code that needs to work properly with both old- and new-style regexes
+can avoid the whole issue by using (for Perls since 5.9.5; see L<re>):
+
+ use re qw(regexp_pattern);
+ my ($pat, $mods) = regexp_pattern($re_ref);
+
+If the actual stringification is important, or older Perls need to be
+supported, you can use something like the following:
+
+ # Accept both old and new-style stringification
+ my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism';
+
+And then use C<$modifiers> instead of C<-xism>.
+
+=head3 Run-time code blocks in regular expressions inherit pragmata
+
+Code blocks in regular expressions (C<(?{...})> and C<(??{...})>) used not
+to inherit any pragmata (strict, warnings, etc.) if the regular expression
+was compiled at run time as happens in cases like these two:
+
+ use re 'eval';
+ $foo =~ $bar; # when $bar contains (?{...})
+ $foo =~ /$bar(?{ $finished = 1 })/;
+
+This was a bug, which has now been fixed. But it has the potential to break
+any code that was relying on it.
+
+=head2 Stashes and Package Variables
+
+=head3 Localised tied hashes and arrays are no longed tied
In the following:
and has now been fixed. This fix could however potentially cause a change
in behaviour of some code.
-=head2 C<given> return values
-
-C<given> blocks now return the last evaluated
-expression, or an empty list if the block was exited by C<break>. Thus you
-can now write:
-
- my $type = do {
- given ($num) {
- break when undef;
- 'integer' when /^[+-]?[0-9]+$/;
- 'float' when /^[+-]?[0-9]+(?:\.[0-9]+)?$/;
- 'unknown';
- }
- };
-
-See L<perlsyn/Return value> for details.
-
-=head2 Naming fixes in Policy_sh.SH may invalidate Policy.sh
-
-Several long-standing typos and naming confusions in Policy_sh.SH have
-been fixed, standardizing on the variable names used in config.sh.
-
-This will change the behavior of Policy.sh if you happen to have been
-accidentally relying on the Policy.sh incorrect behavior.
-
-=head2 Stashes are now always defined
+=head3 Stashes are now always defined
C<defined %Foo::> now always returns true, even when no symbols have yet been
defined in that package.
determine whether an arbitrary hash is empty. Instead, use the behaviour
that an empty C<%hash> always returns false in a scalar context.
-=head2 \400 - \777
+=head3 Dereferencing typeglobs
-Use of C<\400> - C<\777> in regexes in certain circumstances has given
-different, anomalous behavior than their use in all other
-double-quote-like contexts. Since 5.10.1, a deprecated warning message
-has been raised when this happens. Now, all double-quote-like contexts
-have the same behavior, namely to be equivalent to C<\x{100}> -
-C<\x{1FF}>, with no deprecation warning. Use of these values in the
-command line option C<"-0"> retains the current meaning to slurp input
-files whole; previously, this was documented only for C<"-0777">. It is
-recommended, however, because of various ambiguities, to use the new
-C<\o{...}> construct to represent characters in octal.
-
-=head2 Check API compatibility when loading XS modules
+If you assign a typeglob to a scalar variable:
-When perl's API changes in incompatible ways (which usually happens between
-major releases), XS modules compiled for previous versions of perl will not
-work anymore. They will need to be recompiled against the new perl.
+ $glob = *foo;
-In order to ensure that modules are recompiled, and to prevent users from
-accidentally loading modules compiled for old perls into newer ones, the
-C<XS_APIVERSION_BOOTCHECK> macro has been added. That macro, which is called
-when loading every newly compiled extension, compares the API version of the
-running perl with the version a module has been compiled for and raises an
-exception if they don't match.
+the glob that is copied to C<$glob> is marked with a special flag
+indicating that the glob is just a copy. This allows subsequent assignments
+to C<$glob> to overwrite the glob. The original glob, however, is
+immutable.
-=head2 Binary-incompatible with all previous Perls
+Many Perl operators did not distinguish between these two types of globs.
+This would result in strange behaviour in edge cases: C<untie $scalar>
+would do nothing if the last thing assigned to the scalar was a glob
+(because it treated it as C<untie *$scalar>, which unties a handle).
+Assignment to a glob slot (e.g., C<*$glob = \@some_array>) would simply
+assign C<\@some_array> to C<$glob>.
-Perl 5.14.0 is not binary-compatible with any previous stable release.
+To fix this, the C<*{}> operator (including the C<*foo> and C<*$foo> forms)
+has been modified to make a new immutable glob if its operand is a glob
+copy. Various operators that make a distinction between globs and scalars
+have been modified to treat only immutable globs as globs. (C<tie>,
+C<tied> and C<untie> has been left as they are for compatibility's sake,
+but will warn. See L</Deprecations>.)
-=head2 Change in the parsing of certain prototypes
+This causes an incompatible change in code that assigns a glob to the
+return value of C<*{}> when that operator was passed a glob copy. Take the
+following code, for instance:
-Functions declared with the following prototypes now behave correctly as unary
-functions:
+ $glob = *foo;
+ *$glob = *bar;
- *
- \$ \% \@ \* \&
- \[...]
- ;$ ;*
- ;\$ ;\% etc.
- ;\[...]
+The C<*$glob> on the second line returns a new immutable glob. That new
+glob is made an alias to C<*bar>. Then it is discarded. So the second
+assignment has no effect.
-Due to this bug fix [perl #75904], functions
-using the C<(*)>, C<(;$)> and C<(;*)> prototypes
-are parsed with higher precedence than before. So in the following example:
+The upside to this incompatible change is that bugs [perl #77496],
+[perl #77502], [perl #77508], [perl #77688], and [perl #77812],
+and maybe others, too, have been fixed.
- sub foo($);
- foo $a < $b;
+See L<http://rt.perl.org/rt3/Public/Bug/Display.html?id=77810> for even
+more detail.
-the second line is now parsed correctly as C<< foo($a) < $b >>, rather than
-C<< foo($a < $b) >>. This happens when one of these operators is used in
-an unparenthesised argument:
+=head3 Clearing stashes
- < > <= >= lt gt le ge
- == != <=> eq ne cmp ~~
- &
- | ^
- &&
- || //
- .. ...
- ?:
- = += -= *= etc.
+Stash list assignment C<%foo:: = ()> used to make the stash anonymous
+temporarily while it was being emptied. Consequently, any of its
+subroutines referenced elsewhere would become anonymous (showing up as
+"(unknown)" in C<caller>). Now they retain their package names, such that
+C<caller> will return the original sub name if there is still a reference
+to its typeglob, or "foo::__ANON__" otherwise [perl #79208].
-=head2 Magic variables outside the main package
+=head3 Magic variables outside the main package
In previous versions of Perl, magic variables like C<$!>, C<%SIG>, etc. would
'leak' into other packages. So C<%foo::SIG> could be used to access signals,
This has been fixed (or the feature has been removed, depending on how you see
it).
-=head2 Smart-matching against array slices
-
-Previously, the following code resulted in a successful match:
-
- my @a = qw(a y0 z);
- my @b = qw(a x0 z);
- @a[0 .. $#b] ~~ @b;
-
-This odd behaviour has now been fixed [perl #77468].
-
-=head2 C API changes
-
-The first argument of the C API function C<Perl_fetch_cop_label> has changed
-from C<struct refcounted he *> to C<COP *>, to better insulate the user from
-implementation details.
-
-This API function was marked as "may change", and likely isn't in use outside
-the core. (Neither an unpacked CPAN, nor Google's codesearch, finds any other
-references to it.)
+=head2 Changes to Syntax or to Perl Operators
-=head2 Stringification of regexes has changed
+=head3 C<given> return values
-Default regular expression modifiers are now notated by using
-C<(?^...)>. Code relying on the old stringification will fail. The
-purpose of this is so that when new modifiers are added, such code will
-not have to change (after this one time), as the stringification will
-automatically incorporate the new modifiers.
-
-Code that needs to work properly with both old- and new-style regexes
-can avoid the whole issue by using (for Perls since 5.9.5; see L<re>):
-
- use re qw(regexp_pattern);
- my ($pat, $mods) = regexp_pattern($re_ref);
-
-If the actual stringification is important, or older Perls need to be
-supported, you can use something like the following:
-
- # Accept both old and new-style stringification
- my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism';
-
-And then use C<$modifiers> instead of C<-xism>.
-
-=head2 Regular expressions retain their localeness when interpolated
-
-Regular expressions compiled under C<"use locale"> now retain this when
-interpolated into a new regular expression compiled outside a
-C<"use locale">, and vice-versa.
-
-Previously, a regular expression interpolated into another one inherited
-the localeness of the surrounding one, losing whatever state it
-originally had. This is considered a bug fix, but may trip up code that
-has come to rely on the incorrect behavior.
-
-=head2 Directory handles not copied to threads
-
-On systems that do not have a C<fchdir> function, newly-created threads no
-longer inherit directory handles from their parent threads. Such programs
-would probably have crashed anyway [perl #75154].
+C<given> blocks now return the last evaluated
+expression, or an empty list if the block was exited by C<break>. Thus you
+can now write:
-=head2 Negation treats strings differently from before
+ my $type = do {
+ given ($num) {
+ break when undef;
+ 'integer' when /^[+-]?[0-9]+$/;
+ 'float' when /^[+-]?[0-9]+(?:\.[0-9]+)?$/;
+ 'unknown';
+ }
+ };
-The unary negation operator C<-> now treats strings that look like numbers
-as numbers [perl #57706].
+See L<perlsyn/Return value> for details.
-=head2 Negative zero
+=head3 Change in the parsing of certain prototypes
-Negative zero (-0.0), when converted to a string, now becomes "0" on all
-platforms. It used to become "-0" on some, but "0" on others.
+Functions declared with the following prototypes now behave correctly as unary
+functions:
-If you still need to determine whether a zero is negative, use
-C<sprintf("%g", $zero) =~ /^-/> or the L<Data::Float> module on CPAN.
+ *
+ \$ \% \@ \* \&
+ \[...]
+ ;$ ;*
+ ;\$ ;\% etc.
+ ;\[...]
-=head2 Dereferencing typeglobs
+Due to this bug fix [perl #75904], functions
+using the C<(*)>, C<(;$)> and C<(;*)> prototypes
+are parsed with higher precedence than before. So in the following example:
-If you assign a typeglob to a scalar variable:
+ sub foo($);
+ foo $a < $b;
- $glob = *foo;
+the second line is now parsed correctly as C<< foo($a) < $b >>, rather than
+C<< foo($a < $b) >>. This happens when one of these operators is used in
+an unparenthesised argument:
-the glob that is copied to C<$glob> is marked with a special flag
-indicating that the glob is just a copy. This allows subsequent assignments
-to C<$glob> to overwrite the glob. The original glob, however, is
-immutable.
+ < > <= >= lt gt le ge
+ == != <=> eq ne cmp ~~
+ &
+ | ^
+ &&
+ || //
+ .. ...
+ ?:
+ = += -= *= etc.
-Many Perl operators did not distinguish between these two types of globs.
-This would result in strange behaviour in edge cases: C<untie $scalar>
-would do nothing if the last thing assigned to the scalar was a glob
-(because it treated it as C<untie *$scalar>, which unties a handle).
-Assignment to a glob slot (e.g., C<*$glob = \@some_array>) would simply
-assign C<\@some_array> to C<$glob>.
+=head3 Smart-matching against array slices
-To fix this, the C<*{}> operator (including the C<*foo> and C<*$foo> forms)
-has been modified to make a new immutable glob if its operand is a glob
-copy. Various operators that make a distinction between globs and scalars
-have been modified to treat only immutable globs as globs.
+Previously, the following code resulted in a successful match:
-This causes an incompatible change in code that assigns a glob to the
-return value of C<*{}> when that operator was passed a glob copy. Take the
-following code, for instance:
+ my @a = qw(a y0 z);
+ my @b = qw(a x0 z);
+ @a[0 .. $#b] ~~ @b;
- $glob = *foo;
- *$glob = *bar;
+This odd behaviour has now been fixed [perl #77468].
-The C<*$glob> on the second line returns a new immutable glob. That new
-glob is made an alias to C<*bar>. Then it is discarded. So the second
-assignment has no effect.
+=head3 Negation treats strings differently from before
-The upside to this incompatible change is that bugs [perl #77496],
-[perl #77502], [perl #77508], [perl #77688], and [perl #77812],
-and maybe others, too, have been fixed.
+The unary negation operator C<-> now treats strings that look like numbers
+as numbers [perl #57706].
-See L<http://rt.perl.org/rt3/Public/Bug/Display.html?id=77810> for even
-more detail.
+=head3 Negative zero
-=head2 Clearing stashes
+Negative zero (-0.0), when converted to a string, now becomes "0" on all
+platforms. It used to become "-0" on some, but "0" on others.
-Stash list assignment C<%foo:: = ()> used to make the stash anonymous
-temporarily while it was being emptied. Consequently, any of its
-subroutines referenced elsewhere would become anonymous (showing up as
-"(unknown)" in C<caller>). Now they retain their package names, such that
-C<caller> will return the original sub name if there is still a reference
-to its typeglob, or "foo::__ANON__" otherwise [perl #79208].
+If you still need to determine whether a zero is negative, use
+C<sprintf("%g", $zero) =~ /^-/> or the L<Data::Float> module on CPAN.
-=head2 C<:=> is now a syntax error
+=head3 C<:=> is now a syntax error
Previously C<my $pi := 4;> was exactly equivalent to C<my $pi : = 4;>,
with the C<:> being treated as the start of an attribute list, ending before
because of a code generator) then avoid the error by adding a space before
the C<=>.
-=head2 Run-time code block in regular expressions
-
-Code blocks in regular expressions (C<(?{...})> and C<(??{...})>) used not
-to inherit any pragmata (strict, warnings, etc.) if the regular expression
-was compiled at run time as happens in cases like these two:
+=head2 Threads and Processes
- use re 'eval';
- $foo =~ $bar; # when $bar contains (?{...})
- $foo =~ /$bar(?{ $finished = 1 })/;
+=head3 Directory handles not copied to threads
-This was a bug, which has now been fixed. But it has the potential to break
-any code that was relying on this bug.
+On systems other than Windows that do not have
+a C<fchdir> function, newly-created threads no
+longer inherit directory handles from their parent threads. Such programs
+would usually have crashed anyway [perl #75154].
-=head2 Most C<\p{}> properties are now immune from case-insensitive matching
+=head3 C<close> on shared pipes
-For most Unicode properties, it doesn't make sense to have them match
-differently under C</i> case-insensitive matching than not. And doing
-so leads to unexpected results and potential security holes. For
-example
+The C<close> function no longer waits for the child process to exit if the
+underlying file descriptor is still in use by another thread, to avoid
+deadlocks. It returns true in such cases.
- m/\p{ASCII_Hex_Digit}+/i
+=head3 fork() emulation will not wait for signalled children
-could previously match non-ASCII characters because of the Unicode
-matching rules. There were a number of bugs in this feature until an
-earlier release in the 5.13 series. Now this release reverts, and
-removes the feature completely except for the few properties where
-people have come to expect it, namely the ones where casing is an
-integral part of their functionality, such as C<m/\p{Uppercase}/i> and
-C<m/\p{Lowercase}/i>, both of which match the exact same code points,
-namely those matched by C<m/\p{Cased}/i>. Details are in
-L<perlrecharclass/Unicode Properties>.
+On Windows parent processes would not terminate until all forked
+childred had terminated first. However, C<kill('KILL', ...)> is
+inherently unstable on pseudo-processes, and C<kill('TERM', ...)>
+might not get delivered if the child if blocked in a system call.
-XXX The mention of ‘until an earlier release in the 5.13 series’ needs to
-change, but I do not fully understand what happened here.
+To avoid the deadlock and still provide a safe mechanism to terminate
+the hosting process, Perl will now no longer wait for children that
+have been sent a SIGTERM signal. It is up to the parent process to
+waitpid() for these children if child clean-up processing must be
+allowed to finish. However, it is also the responsibility of the
+parent then to avoid the deadlock by making sure the child process
+can't be blocked on I/O either.
-User-defined property handlers that need to match differently under
-C</i> must change to read the new boolean parameter passed to it which is
-non-zero if case-insensitive matching is in effect or 0 otherwise. See
-L<perluniprops/User-Defined Character Properties>.
+See L<perlfork> for more information about the fork() emulation on
+Windows.
-=head2 regex: \p{} in pattern implies Unicode semantics
+=head2 Configuration
-Now, a Unicode property match specified in the pattern will indicate
-that the pattern is meant for matching according to Unicode rules, the way
-C<\x{}> does.
+=head3 Naming fixes in Policy_sh.SH may invalidate Policy.sh
-=head2 GvCV() and GvGP() are no longer lvalues
+Several long-standing typos and naming confusions in Policy_sh.SH have
+been fixed, standardizing on the variable names used in config.sh.
-The new GvCV_set() and GvGP_set() macros are now provided to replace
-assignment to those two macros.
+This will change the behavior of Policy.sh if you happen to have been
+accidentally relying on the Policy.sh incorrect behavior.
-This allows a future commit to eliminate some backref magic between GV
-and CVs, which will require complete control over assignment to the
-gp_cv slot.
+=head2 C API changes
-=head2 C<close> on shared pipes
+=head3 Check API compatibility when loading XS modules
-The C<close> function no longer waits for the child process to exit if the
-underlying file descriptor is still in use by another thread, to avoid
-deadlocks. It returns true in such cases.
+When perl's API changes in incompatible ways (which usually happens between
+major releases), XS modules compiled for previous versions of perl will not
+work anymore. They will need to be recompiled against the new perl.
-=head1 Deprecations
+In order to ensure that modules are recompiled, and to prevent users from
+accidentally loading modules compiled for old perls into newer ones, the
+C<XS_APIVERSION_BOOTCHECK> macro has been added. That macro, which is called
+when loading every newly compiled extension, compares the API version of the
+running perl with the version a module has been compiled for and raises an
+exception if they don't match.
-The following items are now deprecated.
+=head3 Perl_fetch_cop_label
-=over 4
+The first argument of the C API function C<Perl_fetch_cop_label> has changed
+from C<struct refcounted he *> to C<COP *>, to better insulate the user from
+implementation details.
-=item C<Perl_ptr_table_clear>
+This API function was marked as "may change", and likely isn't in use outside
+the core. (Neither an unpacked CPAN, nor Google's codesearch, finds any other
+references to it.)
-C<Perl_ptr_table_clear> 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.
+=head3 GvCV() and GvGP() are no longer lvalues
-=item *
+The new GvCV_set() and GvGP_set() macros are now provided to replace
+assignment to those two macros.
-Omitting a space between a regex pattern or pattern modifiers and the following
-word is deprecated. For example, C<< m/foo/sand $bar >> will still be parsed
-as C<< m/foo/s and $bar >> but will issue a warning.
+This allows a future commit to eliminate some backref magic between GV
+and CVs, which will require complete control over assignment to the
+gp_cv slot.
-=back
+=head1 Deprecations
=head2 Omitting a space between a regular expression and subsequent word
-Omitting a space between a regex pattern or pattern modifiers and the
-following word is deprecated. Deprecation for regular expression
-I<matches> was added in Perl 5.13.2. In this release, the deprecation
-is extended to regular expression I<substitutions>. For example,
-C<< s/foo/bar/sand $bar >> will still be parsed as
-C<< s/foo/bar/s and $bar >> but will issue a warning. (aa78b66)
+Omitting a space between a regular expression operator or
+its modifiers and the following word is deprecated. For
+example, C<< m/foo/sand $bar >> will still be parsed
+as C<< m/foo/s and $bar >> but will issue a warning.
=head2 Deprecation warning added for deprecated-in-core .pl libs
This is a mandatory warning, not obeying -X or lexical warning bits.
The warning is modelled on that supplied by deprecate.pm for
deprecated-in-core .pm libraries. It points to the specific CPAN
-distribution that contains the .pl libraries. The CPAN version, of
-course, does not generate the warning. (0111154)
+distribution that contains the .pl libraries. The CPAN version, of
+course, does not generate the warning.
=head2 List assignment to C<$[>
-After assignment to C<$[> has been deprecated and started to give warnings in
-perl version 5.12.0, this version of perl also starts to emit a warning when
-assigning to C<$[> in list context. This fixes an oversight in 5.12.0.
+Assignment to C<$[> was deprecated and started to give warnings in
+Perl version 5.12.0. This version of perl also starts to emit a warning when
+assigning to C<$[> in list context. This fixes an oversight in 5.12.0.
=head2 Use of qw(...) as parentheses
for $x qw(a b c) { ... }
The parser no longer lies to itself in this way. Wrap the list literal in
-parentheses, like:
+parentheses, like this:
for $x (qw(a b c)) { ... }
a warning. This is to allow future use of C<?> in new operators.
The match-once functionality is still available in the form of C<m?PATTERN?>.
-=head2 C<sv_compile_2op()> is now deprecated
-
-The C<sv_compile_2op()> API function is now deprecated. Searches suggest
-that nothing on CPAN is using it, so this should have zero impact.
-
-It attempted to provide an API to compile code down to an optree, but failed
-to bind correctly to lexicals in the enclosing scope. It's not possible to
-fix this problem within the constraints of its parameters and return value.
-
=head2 Tie functions on scalars holding typeglobs
Calling a tie function (C<tie>, C<tied>, C<untie>) with a scalar argument
a typeglob, and no way to untie a scalar that has had a typeglob
assigned to it.
-This bug was fixed in 5.13.7 but, because of the breakage it caused, the
-fix has been reverted. Now there is a deprecation warning whenever a tie
+Now there is a deprecation warning whenever a tie
function is used on a handle without an explicit C<*>.
-=over
+=head2 User-defined case-mapping
+
+This feature is being deprecated due to its many issues, as documented in
+L<perlunicode/User-Defined Case Mappings (for serious hackers only)>.
+It is planned to remove this feature in Perl 5.16. A CPAN module
+providing improved functionality is being prepared for release by the
+time 5.14 is.
-=item Deprecated Modules
+XXX What module is that?
+
+=head2 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.
+core versions of these modules 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
+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
+install into C<vendor> or C<site> perl library directories. This will
inhibit the deprecation warnings.
Alternatively, you may want to consider patching F<lib/deprecate.pm>
=back
-=back
+=head2 Deprecated C APIs
-=head2 User-defined case-mapping
+=over
-This feature is being deprecated due to its many issues, as documented in
-L<perlunicode/User-Defined Case Mappings (for serious hackers only)>.
-It is planned to remove this feature in Perl 5.16. A CPAN module
-providing improved functionality is being prepared for release by the
-time 5.14 is.
+=item C<Perl_ptr_table_clear>
+
+C<Perl_ptr_table_clear> 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.
+
+=item C<sv_compile_2op>
+
+The C<sv_compile_2op()> API function is now deprecated. Searches suggest
+that nothing on CPAN is using it, so this should have zero impact.
+
+It attempted to provide an API to compile code down to an optree, but failed
+to bind correctly to lexicals in the enclosing scope. It's not possible to
+fix this problem within the constraints of its parameters and return value.
+
+=back
=head1 Performance Enhancements
-=head2 "safe signals" optimization
+=head2 "Safe signals" optimisation
Signal dispatch has been moved from the runloop into control ops. This
should give a few percent speed increase, and eliminates almost all of
create uninterruptible loops, this is a bug, and reports are encouraged
of how to recreate such issues.
-=head2 Optimization of shift; and pop; calls without arguments
+=head2 Optimisation of shift; and pop; calls without arguments
-Additional two OPs are not added anymore into op tree for shift and pop
-calls without argument (when it works on C<@_>). Makes C<shift;> 5%
-faster over C<shift @_;> on not threaded perl and 25% faster on threaded.
+Two fewer OPs are used for shift and pop calls with no argument (with
+implicit C<@_>). This change makes C<shift;> 5% faster than C<shift @_;>
+on non-threaded perls and 25% faster on threaded.
-=head2 Adjacent pairs of nextstate opcodes are now optimized away
+=head2 Optimisation of regexp engine string comparison work
-Previously, in code such as
+The foldEQ_utf8 API function for case-insensitive comparison of strings (which
+is used heavily by the regexp engine) was substantially refactored and
+optimised - and its documentation much improved as a free bonus gift.
- use constant DEBUG => 0;
+=head2 Regular expression compilation speed-up
- sub GAK {
- warn if DEBUG;
- print "stuff\n";
- }
+Compiling regular expressions has been made faster for the case where upgrading
+the regex to utf8 is necessary but that isn't known when the compilation begins.
-the ops for C<warn if DEBUG;> would be folded to a C<null> op (C<ex-const>), but
-the C<nextstate> op would remain, resulting in a runtime op dispatch of
-C<nextstate>, C<nextstate>, ...
+=head2 String appending is 100 times faster
-The execution of a sequence of C<nextstate> ops is indistinguishable from just
-the last C<nextstate> op so the peephole optimizer now eliminates the first of
-a pair of C<nextstate> ops, except where the first carries a label, since labels
-must not be eliminated by the optimizer and label usage isn't conclusively known
-at compile time.
+When doing a lot of string appending, perl could end up allocating a lot more
+memory than needed in a very inefficient way, if perl was configured to use the
+system's C<malloc> implementation instead of its own.
-=head2 blah blah blah
+C<sv_grow>, which is what's being used to allocate more memory if necessary
+when appending to a string, has now been taught how to round up the memory
+it requests to a certain geometric progression, making it much faster on
+certain platforms and configurations. On Win32, it's now about 100 times
+faster.
+
+=head2 Eliminate C<PL_*> accessor functions under ithreads
+
+When C<MULTIPLICITY> was first developed, and interpreter state moved into
+an interpreter struct, thread and interpreter local C<PL_*> variables were
+defined as macros that called accessor functions, returning the address of
+the value, outside of the perl core. The intent was to allow members
+within the interpreter struct to change size without breaking binary
+compatibility, so that bug fixes could be merged to a maintenance branch
+that necessitated such a size change.
+
+However, some non-core code defines C<PERL_CORE>, sometimes intentionally
+to bypass this mechanism for speed reasons, sometimes for other reasons but
+with the inadvertent side effect of bypassing this mechanism. As some of
+this code is widespread in production use, the result is that the core
+I<can't> change the size of members of the interpreter struct, as it will
+break such modules compiled against a previous release on that maintenance
+branch. The upshot is that this mechanism is redundant, and well-behaved
+code is penalised by it. Hence it can and should be removed (and has
+been).
+
+=head2 Freeing weak references
-Only allocate entries for @_ on demand - this not only saves memory per
-subroutine defined but should hopefully improve COW behaviour (77bac2).
+When an object has many weak references to it, freeing that object
+can under some some circumstances take O(N^2) time to free (where N is the
+number of references). The number of circumstances has been reduced
+[perl #75254]
-=head2 Multiple small improvements to threads
+=head2 Lexical array and hash assignments
-The internal structures of threading now make fewer API calls and fewer
-allocations, resulting in noticeably smaller object code. Additionally,
-many thread context checks have been deferred so that they're only done
-when required (although this is only possible for non-debugging builds).
+An earlier optimisation to speed up C<my @array = ...> and
+C<my %hash = ...> assignments caused a bug and was disabled in Perl 5.12.0.
+
+Now we have found another way to speed up these assignments [perl #82110].
+
+=head2 C<@_> uses less memory
+
+Previously, C<@_> was allocated for every subroutine at compile time with
+enough space for four entries. Now this allocation is done on demand when
+the subroutine is called [perl #72416].
=head2 Size optimisations to SV and HV structures
xhv_fill has been eliminated from struct xpvhv, saving 1 IV per hash and
-on some systems will cause struct xpvhv to become cache aligned. To avoid
+on some systems will cause struct xpvhv to become cache-aligned. To avoid
this memory saving causing a slowdown elsewhere, boolean use of HvFILL
now calls HvTOTALKEYS instead (which is equivalent) - so while the fill
-data when actually required is now calculated on demand, the cases when
-this needs to be done should be few and far between (f4431c .. fcd245).
+data when actually required are now calculated on demand, the cases when
+this needs to be done should be few and far between.
-The order of structure elements in SV bodies has changed. Effectively,
-the NV slot has swapped location with STASH and MAGIC. As all access to
-SV members is via macros, this should be completely transparent. This
+The order of structure elements in SV bodies has changed. Effectively,
+the NV slot has swapped location with STASH and MAGIC. As all access to
+SV members is via macros, this should be completely transparent. This
change allows the space saving for PVHVs documented above, and may reduce
the memory allocation needed for PVIVs on some architectures.
-=head2 Optimisation of regexp engine string comparison work
+C<XPV>, C<XPVIV>, and C<XPVNV> now only allocate the parts of the C<SV> body
+they actually use, saving some space.
-The foldEQ_utf8 API function for case-insensitive comparison of strings (which
-is used heavily by the regexp engine) was substantially refactored and
-optimised - and its documentation much improved as a free bonus gift
-(8b3587, e6226b).
+Scalars containing regular expressions now only allocate the part of the C<SV>
+body they actually use, saving some space.
=head2 Memory consumption improvements to Exporter
The @EXPORT_FAIL AV is no longer created unless required, hence neither is
-the typeglob backing it - this saves about 200 bytes per Exporter using
-package that doesn't use this functionality.
-
-=head2 blah blah blah
+the typeglob backing it. This saves about 200 bytes for every package that
+uses Exporter but doesn't use this functionality.
-There are several small optimizations to reduce CPU cache misses in various very
-commonly used modules like C<warnings> and C<Carp> as well in accessing
-file-handles for reading. (5.13.3)
-
-XXX These need to be changed to =head2 entries, or the entries above need
-to change:
-
-=over 4
-
-=item *
-
-Make string appending 100 times faster
-
-When doing a lot of string appending, perl could end up allocating a lot more
-memory than needed in a very inefficient way, if perl was configured to use the
-system's C<malloc> implementation instead of its own.
-
-C<sv_grow>, which is what's being used to allocate more memory if necessary when
-appending to a string, has now been taught how to round up the memory it
-requests to a certain geometric progression, making it much faster on certain
-platforms and configurations. On Win32, it's now about 100 times faster.
-
-=item *
+=head2 Memory savings for weak references
For weak references, the common case of just a single weak reference per
referent has been optimised to reduce the storage required. In this case it
-saves the equivalent of one small perl array per referent.
-
-=item *
-
-C<XPV>, C<XPVIV>, and C<XPVNV> now only allocate the parts of the C<SV> body
-they actually use, saving some space.
-
-=item *
-
-Scalars containing regular expressions now only allocate the part of the C<SV>
-body they actually use, saving some space.
-
-=item *
-
-Compiling regular expressions has been made faster for the case where upgrading
-the regex to utf8 is necessary but that isn't known when the compilation begins.
+saves the equivalent of one small Perl array per referent.
-=item *
+=head2 C<%+> and C<%-> use less memory
The bulk of the C<Tie::Hash::NamedCapture> module used to be in the perl
-core. It has now been moved to an XS module, to reduce the overhead for
+core. It has now been moved to an XS module, to reduce the overhead for
programs that do not use C<%+> or C<%->.
-=item *
-
-Eliminate C<PL_*> accessor functions under ithreads.
-
-When C<MULTIPLICITY> was first developed, and interpreter state moved into an
-interpreter struct, thread and interpreter local C<PL_*> variables were defined
-as macros that called accessor functions, returning the address of the value,
-outside of the perl core. The intent was to allow members within the interpreter
-struct to change size without breaking binary compatibility, so that bug fixes
-could be merged to a maintenance branch that necessitated such a size change.
-
-However, some non-core code defines C<PERL_CORE>, sometimes intentionally to
-bypass this mechanism for speed reasons, sometimes for other reasons but with
-the inadvertent side effect of bypassing this mechanism. As some of this code is
-widespread in production use, the result is that the core B<can't> change the
-size of members of the interpreter struct, as it will break such modules
-compiled against a previous release on that maintenance branch. The upshot is
-that this mechanism is redundant, and well-behaved code is penalised by
-it. Hence it can and should be removed.
+=head2 Multiple small improvements to threads
-=item *
+The internal structures of threading now make fewer API calls and fewer
+allocations, resulting in noticeably smaller object code. Additionally,
+many thread context checks have been deferred so that they're only done
+when required (although this is only possible for non-debugging builds).
-When an object has many weak references to it, freeing that object
-can under some some circumstances take O(N^2) time to free (where N is the
-number of references). The number of circumstances has been reduced
-[perl #75254]
+=head2 Adjacent pairs of nextstate opcodes are now optimized away
-=item *
+Previously, in code such as
-An earlier optimisation to speed up C<my @array = ...> and
-C<my %hash = ...> assignments caused a bug and was disabled in Perl 5.12.0.
+ use constant DEBUG => 0;
-Now we have found another way to speed up these assignments [perl #82110].
+ sub GAK {
+ warn if DEBUG;
+ print "stuff\n";
+ }
-=back
+the ops for C<warn if DEBUG;> would be folded to a C<null> op (C<ex-const>), but
+the C<nextstate> op would remain, resulting in a runtime op dispatch of
+C<nextstate>, C<nextstate>, ....
+
+The execution of a sequence of C<nextstate> ops is indistinguishable from just
+the last C<nextstate> op so the peephole optimizer now eliminates the first of
+a pair of C<nextstate> ops, except where the first carries a label, since labels
+must not be eliminated by the optimizer and label usage isn't conclusively known
+at compile time.
=head1 Modules and Pragmata
=item *
-XXX Where does this go in the list?
+C<Archive::Extract> has been upgraded from version 0.38 to 0.48.
+
+Updates since 0.38 include: a safe print method that guards
+Archive::Extract from changes to $\; a fix to the tests when run in core
+perl; support for TZ files; a modification for the lzma
+logic to favour IO::Uncompress::Unlzma; and a fix
+for an issue with NetBSD-current and its new unzip
+executable.
+
+=item *
+
+C<Archive::Tar> has been upgraded from version 1.54 to 1.76.
-Perl 4 C<.pl> libraries
+Important changes since 1.54 include the following:
-These historical libraries have been minimally modified to avoid using
-C<$[>. This is to prepare them for the deprecation of C<$[>.
+=over
=item *
-C<Archive::Extract> has been upgraded from version 0.38 to 0.48.
+Compatibility with busybox implementations of tar
-Updates since 0.38 include: a safe print method that guards
-Archive::Extract from changes to $\; a fix to the tests when run in core
-perl; support for TZ files; and a modification for the lzma logic to favour
-IO::Uncompress::Unlzma
+=item *
-Resolves an issue with NetBSD-current and its new unzip
-executable.
+A fix so that C<write()> and C<create_archive()>
+close only handles they opened
=item *
-C<Archive::Tar> has been upgraded from version 1.54 to 1.76.
+A bug was fixed regarding the exit code of extract_archive.
-Important changes since 1.54 include: compatibility with busybox
-implementations of tar; a fix so that C<write()> and C<create_archive()>
-close only handles they opened; and a bug was fixed regarding the exit code
-of extract_archive. (afabe0e)
+=item *
-Among other things, the new version adds a new option to C<ptar> to allow safe
+C<ptar> has a new option to allow safe
creation of tarballs without world-writable files on Windows, allowing those
archives to be uploaded to CPAN.
-This adds the ptargrep utility for using regular expressions against
-the contents of files in a tar archive.
+=item *
-Skip extracting pax extended headers.
+A new ptargrep utility for using regular expressions against
+the contents of files in a tar archive.
=item *
-C<autodie> has been upgraded from version 2.06_01 to 2.1001.
+Pax extended headers are now skipped.
+
+=back
=item *
=item *
-C<B::Debug> has been upgraded from version 1.12 to 1.16.
-
-=item *
-
C<B::Deparse> has been upgraded from version 0.96 to 1.02.
-A bug has been fixed when deparsing a nextstate op that has both a
+The deparsing of a nextstate op has changed when it has both a
change of package (relative to the previous nextstate), or a change of
C<%^H> or other state, and a label. Previously the label was emitted
-first, leading to syntactically invalid output because a label is not
-permitted immediately before a package declaration, B<BEGIN> block,
-or some other things. Now the label is emitted last.
+first, but now the label is emitted last.
-The 'no 5.13.2' or similar form is now correctly handled by B::Deparse.
+The C<no 5.13.2> or similar form is now correctly handled by B::Deparse.
B::Deparse now properly handles the code that applies a conditional
pattern match against implicit C<$_> as it was fixed in [perl #20444].
-It fixes deparsing of C<our> followed by a variable with funny characters
-(as permitted under the C<utf8> pragma) [perl #33752].
-
-=item *
-
-C<B::Lint> has been upgraded from version 1.11_01 to 1.12.
-
-=item *
-
-C<base> has been upgraded from version 2.15 to 2.16.
-
-=item *
-
-C<bignum> has been upgraded from version 0.23 to 0.25.
-
-=item *
-
-C<blib> has been upgraded from version 1.04 to 1.06.
+Deparsing of C<our> followed by a variable with funny characters
+(as permitted under the C<utf8> pragma) has also been fixed [perl #33752].
=item *
This fixes certain cases of C<Bizarre copy of ARRAY> caused by modules
overriding C<caller()> incorrectly.
-It now avoids using regular expressions that cause perl to
+It now also avoids using regular expressions that cause perl to
load its Unicode tables, in order to avoid the 'BEGIN not safe after
errors' error that will ensue if there has been a syntax error
[perl #82854].
C<CGI> has been upgraded from version 3.48 to 3.51.
This provides the following security fixes: the MIME boundary in
-multipart_init is now random and improvements to the handling of
-newlines embedded in header values.
-
-The documentation for param_fetch() has been corrected and clarified.
-
-=item *
-
-C<charnames> has been upgraded from version 1.07 to 1.10.
-
-C<viacode()> is now significantly faster.
+multipart_init is now random and the handling of
+newlines embedded in header values has been improved.
=item *
C<Compress::Raw::Bzip2> has been upgraded from version 2.024 to 2.033.
-Updated to use bzip2 1.0.6
+It has been updated to use bzip2 1.0.6.
=item *
-C<Compress::Raw::Zlib> has been upgraded from version 2.024 to 2.033.
+C<CPAN> has been upgraded from version 1.94_56 to 1.9600.-
-=item *
+Major highlights:
-C<Compress::Zlib> has been upgraded from version 2.024 to 2.027.
+=over 4
-=item *
+=item * much less configuration dialog hassle
-C<CPAN> has been upgraded from version 1.94_56 to 1.9600.
+=item * support for META/MYMETA.json
-=over 4
+=item * support for local::lib
-=item * release 1.94_57
+=item * support for HTTP::Tiny to reduce the dependency on ftp sites
-=item * bugfix: treat modules correctly that are deprecated in perl 5.12.
+=item * automatic mirror selection
-=item * bugfix: RT #57482 and #57788 revealed that configure_requires
-implicitly assumed build_requires instead of normal requires. (Reported
-by Andrew Whatson and Father Chrysostomos respectively)
+=item * iron out all known bugs in configure_requires
-=item * testfix: solaris should run the tests without expect because (some?)
-solaris have a broken expect
+=item * support for distributions compressed with bzip2
-=item * testfix: run tests with cache_metadata off to prevent spill over
-effects from previous test runs
+=item * allow Foo/Bar.pm on the commandline to mean Foo::Bar
=back
-Includes support for META.json and MYMETA.json.
-
=item *
C<CPANPLUS> has been upgraded from version 0.90 to 0.9102.
-Fixed the shell test to skip if test is not being run under a terminal;
-resolved the issue where a prereq on Config would not be recognised as a
-core module.
-
-Includes support for META.json and MYMETA.json and a change to
-using Digest::SHA for CPAN checksums.
-
-=item *
-
-C<CPANPLUS::Dist::Build> has been upgraded from version 0.46 to 0.54.
-
-=item *
+A dependency on Config was not recognised as a
+core module dependency. This has been fixed.
-C<Cwd> has been upgraded from version 3.31 to 3.36.
+CPANPLUS now includes support for META.json and MYMETA.json.
=item *
The indentation used to be off when C<$Data::Dumper::Terse> was set. This
has been fixed [perl #73604].
-This fixes a crash when using custom sort functions that might cause the stack
-to change.
+This upgrade also fixes a crash when using custom sort functions that might
+cause the stack to change [perl #74170].
C<Dumpxs> no longer crashes with globs returned by C<*$io_ref>
[perl #72332].
=item *
-C<DB_File> has been upgraded from version 1.820 to 1.821.
-
-=item *
-
-C<deprecate> has been upgraded from version 0.01 to 0.02.
-
-=item *
-
C<Devel::DProf> has been upgraded from version 20080331.00 to 20110228.00.
Merely loading C<Devel::DProf> now no longer triggers profiling to start.
the profiler.
NOTE: C<Devel::DProf> is deprecated and will be removed from a future
-version of Perl. We strongly recommend that you install and use
+version of Perl. We strongly recommend that you install and use
L<Devel::NYTProf> instead, as it offers significantly improved
profiling and reporting.
=item *
-C<Devel::Peek> has been upgraded from version 1.04 to 1.06.
-
-=item *
-
-C<Devel::SelfStubber> has been upgraded from version 1.03 to 1.05.
-
-=item *
-
C<diagnostics> has been upgraded from version 1.19 to 1.22.
It now renders pod links slightly better, and has been taught to find
C<Addfile> accepts all POSIX filenames.
-New SHA-512/224 and SHA-512/256 transforms ref. NIST Draft FIPS 180-4 (February 2011)
-
-=item *
-
-C<Dumpvalue> has been upgraded from version 1.13 to 1.15.
+New SHA-512/224 and SHA-512/256 transforms (ref. NIST Draft FIPS 180-4
+[February 2011])
=item *
C<Encode> has been upgraded from version 2.39 to 2.42.
Now, all 66 Unicode non-characters are treated the same way U+FFFF has
-always been treated; if it was disallowed, all 66 are disallowed; if it
-warned, all 66 warn.
-
-=item *
-
-C<Env> has been upgraded from version 1.01 to 1.02.
+always been treated; in cases when it was disallowed, all 66 are
+disallowed; in those cases where it warned, all 66 warn.
=item *
C<Errno> has been upgraded from version 1.11 to 1.13.
The implementation of C<Errno> has been refactored to use about 55% less memory.
-There should be no user-visible changes.
On some platforms with unusual header files, like Win32/gcc using mingw64
headers, some constants which weren't actually error numbers have been exposed
=item *
-C<ExtUtils::CBuilder> has been upgraded from 0.27 to 0.280201.
-
-Handle C and C++ compilers separately.
-
-Preserves exit status on VMS.
-
-=item *
-
-C<ExtUtils::Command> has been upgraded from version 1.16 to 1.17.
-
-=item *
-
C<ExtUtils::Constant> has been upgraded from 0.22 to 0.23.
The C<AUTOLOAD> helper code generated by C<ExtUtils::Constant::ProxySubs>
can now C<croak> for missing constants, or generate a complete C<AUTOLOAD>
-subroutine in XS, allowing simplification of many modules that use it.
-(C<Fcntl>, C<File::Glob>, C<GDBM_File>, C<I18N::Langinfo>, C<POSIX>, C<Socket>)
+subroutine in XS, allowing simplification of many modules that use it
+(C<Fcntl>, C<File::Glob>, C<GDBM_File>, C<I18N::Langinfo>, C<POSIX>,
+C<Socket>).
C<ExtUtils::Constant::ProxySubs> can now optionally push the names of all
-constants onto the package's C{@EXPORT_OK}. This has been used to replace
-less space-efficient code in C<B>, helping considerably shrink the size of its
-shared object.
-
-=item *
-
-C<ExtUtils::Constant::Utils> has been upgraded from 0.02 to 0.03.
-
-Refactoring and fixing of backcompat code, preparing for resynchronisation
-with CPAN.
-
-=item *
-
-C<ExtUtils::Embed> has been upgraded from 1.28 to 1.30.
-
-=item *
-
-C<ExtUtils::MakeMaker> has been upgraded from version 6.56 to 6.57_05.
-
-=item *
-
-C<ExtUtils::Manifest> has been upgraded from version 1.57 to 1.58.
-
-=item *
-
-C<ExtUtils::ParseXS> has been upgraded from 2.21 to 2.2208.
-
-=item *
-
-C<Fcntl> has been upgraded from 1.06 to 1.11.
-
-=item *
-
-C<File::Copy> has been downgraded from version 2.17 to 2.21.
-
-An extra stanza was added explaining behaviours when the copy destination
-already exists and is a directory.
+constants onto the package's C<@EXPORT_OK>.
=item *
C<File::DosGlob> has been upgraded from version 1.01 to 1.03.
It allows patterns containing literal parentheses (they no longer need to
-be escaped). On Windows, it no longer adds an extra F<./> to the file names
+be escaped). On Windows, it no longer
+adds an extra F<./> to the file names
returned when the pattern is a relative glob with a drive specification,
like F<c:*.pl> [perl #71712].
C<File::Find> has been upgraded from version 1.15 to 1.18.
-It improves handling of backslashes on Windows, so that paths such as
+It improves handling of backslashes on Windows, so that paths like
F<c:\dir\/file> are no longer generated [perl #71710].
=item *
-C<feature> has been upgraded from 1.16 to 1.19.
-
-Documentation and test updates for the C<unicode_strings> feature.
-See L</Full functionality for C<use feature 'unicode_strings'>>.
-
-=item *
-
-C<File::CheckTree> has been upgraded from 4.4 to 4.41.
-
-=item *
-
-C<File::Glob> has been upgraded from 1.07 to 1.11.
-
-=item *
-
C<File::stat> has been upgraded from 1.02 to 1.04.
The C<-x> and C<-X> file test operators now work correctly under the root
=item *
-C<Filter::Simple> has been upgraded from version 0.84 to 0.85.
-
-=item *
-
C<GDBM_File> has been upgraded from 1.10 to 1.13.
This fixes a memory leak when DBM filters are used.
C<Hash::Util> has been upgraded from 0.07 to 0.10.
-Hash::Util now enables "no warnings 'uninitialized'" to suppress spurious
-warnings from undefined hash values (RT #74280).
-
-=item *
-
-C<Hash::Util::FieldHash> has been upgraded from 1.04 to 1.07.
-
-=item *
-
-C<I18N::Collate> has been upgraded from 1.01 to 1.02.
+Hash::Util no longer emits spurious "uninitialized" warnings when
+recursively locking hashes that have undefined values [perl #74280].
=item *
C<I18N::Langinfo> has been upgraded from version 0.03 to 0.07.
C<langinfo()> now defaults to using C<$_> if there is no argument given, just
-like the documentation always claimed it did.
-
-=item *
-
-C<I18N::LangTags> has been upgraded from version 0.35 to 0.35_01.
-
-=item *
-
-C<if> has been upgraded from version 0.05 to 0.0601.
-
-=item *
-
-C<IO> has been upgraded from version 1.25_02 to 1.25_04.
-
-=item *
-
-The IO-Compress distribution has been upgraded from version 2.024 to 2.033.
+as the documentation has always claimed.
=item *
=item *
-C<IO::Socket> has been upgraded from version 1.31 to 1.32.
-
-C<getsockopt> and C<setsockopt> are now documented.
-
-=item *
-
C<IPC::Cmd> has been upgraded from version 0.54 to 0.68.
-Resolves an issue with splitting Win32 command lines.
+Resolves an issue with splitting Win32 command lines. An argument
+consisting of the single character "0" used to be omitted (CPAN RT #62961).
=item *
=item *
-C<IPC::SysV> has been upgraded from version 2.01 to 2.03.
-
-=item *
-
-C<lib> has been upgraded from version 0.62 to 0.63.
-
-=item *
-
-The Locale-Codes distribution has been upgraded from version 2.07 to 3.16.
-
-Locale::Country, Locale::Language and Locale::Currency were updated from
-3.12 to 3.13 of the Locale-Codes distribution to include locale code changes.
-
-Adds some codes.
-
-=item *
-
C<Locale::Maketext> has been upgraded from version 1.14 to 1.17.
-Locale::Maketext guts have been merged back into the main module
-and adds external cache support
+Locale::Maketext now supports external caches.
-It fixes an infinite loop in C<Locale::Maketext::Guts::_compile()> when
+This upgrade also fixes an infinite loop in
+C<Locale::Maketext::Guts::_compile()> when
working with tainted values (CPAN RT #40727).
-C<< ->maketext >> calls will now backup and restore C<$@> so that error
+C<< ->maketext >> calls will now back up and restore C<$@> so that error
messages are not suppressed (CPAN RT #34182).
=item *
-C<Log::Message> has been upgraded from version 0.02 to 0.04.
-
-=item *
-
-C<Log::Message::Simple> has been upgraded from version 0.06 to 0.08.
-
-=item *
-
C<Math::BigInt> has been upgraded from version 1.89_01 to 1.994.
This fixes, among other things, incorrect results when computing binomial
coefficients [perl #77640].
-This prevents C<sqrt($int)> from crashing under C<use bigrat;>
+It also prevents C<sqrt($int)> from crashing under C<use bigrat;>
[perl #73534].
=item *
-C<Math::BigInt::FastCalc> has been upgraded from version 0.19 to 0.28.
-
-=item *
-
-C<Math::BigRat> has been upgraded from version 0.24 to 0.26_01.
-
-=item *
-
-C<Memoize> has been upgraded from version 1.01_03 to 1.02.
-
-=item *
-
C<MIME::Base64> has been upgraded from 3.08 to 3.13.
Includes new functions to calculate the length of encoded and decoded
favor of a standalone copy of it called L<Module::Metadata>.
Module::Build::YAML has been deprecated in favor of L<CPAN::Meta::YAML>.
-Module::Build now also generates META.json and MYMETA.json files
-in accordance with version 2 of the CPAN distribution metadata specification,
-L<CPAN::Meta::Spec>. The older format META.yml and MYMETA.yml files are
-still generated, as well.
-
-=item *
-
-C<Module::CoreList> has been upgraded from version 2.29 to XXX.
-
-Besides listing the updated core modules of this release, it also stops listing
-the C<Filespec> module. That module never existed in core. The scripts
-generating C<Module::CoreList> confused it with C<VMS::Filespec>, which actually
-is a core module, since the time of perl 5.8.7.
-
-=item *
-
-C<Module::Load> has been upgraded from version 0.16 to 0.18.
-
-=item *
-
-C<Module::Load::Conditional> has been upgraded from version 0.34 to 0.40.
-
-=item *
-
-C<Module::Metadata> has been upgraded from version 1.000003 to 1.000004.
-
-XXX This is not listed in corelist for 5.12.0. When was it added?
-
-=item *
-
-C<mro> has been upgraded from version 1.02 to 1.06.
-
-C<next::method> I<et al.> now take into account that every class inherits
-from UNIVERSAL [perl #68654].
-
-=item *
-
-C<NDBM_File> has been upgraded from 1.08 to 1.11.
-
-This fixes a memory leak when DBM filters are used.
-
-=item *
-
-C<NEXT> has been upgraded from version 0.64 to 0.65.
-
-=item *
-
-C<ODBM_File> has been upgraded from 1.08 to 1.09.
-
-This fixes a memory leak when DBM filters are used.
-
-=item *
-
-C<Net::Ping> has been upgraded from 2.36 to 2.37.
-
-=item *
-
-C<ODBM_File> has been upgraded from 1.07 to 1.10.
-
-=item *
-
-C<Object::Accessor> has been upgraded from version 0.36 to 0.38.
-
-=item *
-
-C<open> has been upgraded from version 1.07 to 1.08.
-
-=item *
-
-C<Opcode> has been upgraded from 1.15 to 1.18.
-
-=item *
-
-C<overload> has been upgraded from 1.11 to 1.12.
-
-C<overload::Method> can now handle subroutines that are themselves blessed
-into overloaded classes [perl #71998].
-
-Avoid a taint problem in use of sprintf.
-
-The documentation has greatly improved. See L</Documentation> below.
-
-=item *
-
-C<Params::Check> has been upgraded from version 0.26 to 0.28.
-
-=item *
-
-C<parent> has been upgraded from version 0.223 to 0.225.
-
-=item *
-
-C<Parse::CPAN::Meta> has been upgraded from version 1.40 to 1.4401.
-
-The latest Parse::CPAN::Meta can now read YAML or JSON files using
-L<CPAN::Meta::YAML> and L<JSON::PP>, which are now part of the Perl core.
-
-=item *
-
-The PathTools distribution has been upgraded from version 3.31 to 3.34.
-
-Various issues in L<File::Spec::VMS> have been fixed. (5.13.4)
+Module::Build now also generates META.json and MYMETA.json files
+in accordance with version 2 of the CPAN distribution metadata specification,
+L<CPAN::Meta::Spec>. The older format META.yml and MYMETA.yml files are
+still generated, as well.
=item *
-C<PerlIO::encoding> has been upgraded from 0.12 to 0.14.
+C<Module::CoreList> has been upgraded from version 2.29 to XXX.
+
+Besides listing the updated core modules of this release, it also stops listing
+the C<Filespec> module. That module never existed in core. The scripts
+generating C<Module::CoreList> confused it with C<VMS::Filespec>, which actually
+is a core module as of perl 5.8.7.
=item *
-C<PerlIO::scalar> has been upgraded from 0.07 to 0.11.
+C<NDBM_File> and C<ODBM_File> have been upgraded from 1.08 to 1.11, and
+from 1.08 to 1.09, respectively.
-A C<read> after a C<seek> beyond the end of the string no longer thinks it
-has data to read [perl #78716].
+This fixes a memory leak when DBM filters are used.
=item *
-C<PerlIO::via> has been upgraded from 0.09 to 0.11.
+C<overload> has been upgraded from 1.11 to 1.12.
-=item *
+C<overload::Method> can now handle subroutines that are themselves blessed
+into overloaded classes [perl #71998].
-The podlators distribution has been upgraded from version 2.3.1 to 2.4.0.
+The documentation has greatly improved. See L</Documentation> below.
=item *
-C<Pod::LaTeX> has been upgraded from version 0.58 to 0.59.
+C<Parse::CPAN::Meta> has been upgraded from version 1.40 to 1.4401.
+
+The latest Parse::CPAN::Meta can now read YAML and JSON files using
+L<CPAN::Meta::YAML> and L<JSON::PP>, which are now part of the Perl core.
=item *
-C<Pod::Simple> has been upgraded from 3.14 to 3.15
+C<PerlIO::scalar> has been upgraded from 0.07 to 0.11.
-Includes various fixes to C<HTML> and C<XHTML> handling.
+A C<read> after a C<seek> beyond the end of the string no longer thinks it
+has data to read [perl #78716].
=item *
=item *
-C<re> has been upgraded from version 0.11 to 0.15.
+C<re> has been upgraded from version 0.11 to 0.17.
New C<use re "/flags"> pragma
-Enforce that C</d>, C</u>, and C</l> are mutually exclusive.
-
-C<re> has been upgraded from version 0.16 to 0.17.
-
-It now supports the double-a flag: C<use re '/aa';>
-
The C<regmust> function used to crash when called on a regular expression
-belonging to a pluggable engine. Now it has been disabled for those.
+belonging to a pluggable engine. Now it croaks instead.
C<regmust> no longer leaks memory.
=item *
-C<SDBM_File> has been upgraded from 1.06 to 1.08.
-
-=item *
-
C<SelfLoader> has been upgraded from 1.17 to 1.18.
It now works in taint mode [perl #72062].
=item *
-C<Socket> has been upgraded from version 1.87 to XXX.
-
-It has several new functions for handling IPv6 addresses. (from 5.13.8)
+C<Socket> has been upgraded from version 1.87 to 1.94.
-It provides new affordances for IPv6,
-including implementations of the C<Socket::getaddrinfo()> and
-C<Socket::getnameinfo()> functions, along with related constants.
+See L</IPv6 support>, above.
=item *
Includes performance improvement for overloaded classes.
-=item *
-
-C<Storable> has been upgraded from 2.24 to 2.25.
-
This adds support for serialising code references that contain UTF-8 strings
-correctly. The Storable minor version number changed as a result, meaning that
+correctly. The Storable minor version
+number changed as a result, meaning that
Storable users who set C<$Storable::accept_future_minor> to a C<FALSE> value
will see errors (see L<Storable/FORWARD COMPATIBILITY> for more details).
=item *
-C<Sys::Hostname> has been upgraded from 1.11 to 1.14.
-
-=item *
-
-C<Term::ANSIColor> has been upgraded from version 2.02 to 3.00.
-
-=item *
-
-C<Term::UI> has been upgraded from version 0.20 to 0.26.
-
-=item *
-
-C<Test::Harness> has been upgraded from version 3.17 to 3.23.
-
-The core update from Test-Harness 3.17 to 3.21 fixed some things, but
-also L<introduced a known problem|/"Known Problems"> with argument
-passing to non-Perl tests. (5.13.3)
-
-=item *
-
C<Test::Simple> has been upgraded from version 0.94 to 0.98.
Among many other things, subtests without a C<plan> or C<no_plan> now have an
=item *
-C<Thread::Queue> has been upgraded from version 2.11 to 2.12.
-
-=item *
-
C<Thread::Semaphore> has been upgraded from version 2.09 to 2.12.
-Added new methods -E<gt>down_nb() and -E<gt>down_force() at the suggestion
-of Rick Garlick.
-
-Refactored methods to skip argument validation when no argument is supplied.
-
-=item *
-
-C<threads> has been upgraded from version 1.75 to 1.82.
-
-=item *
-
-C<threads::shared> has been upgraded from version 1.32 to 1.36.
+It provides two new methods that give more control over the decrementing of
+semaphores: C<down_nb> and C<down_force>.
=item *
=item *
-C<Tie::Hash::NamedCapture> has been upgraded from version 0.06 to 0.08.
-
-Some of the Perl code has been converted to XS for efficency's sake.
-
-=item *
-
-C<Tie::RefHash> has been upgraded from version 1.38 to 1.39.
-
-=item *
-
-C<Time::HiRes> has been upgraded from version 1.9719 to 1.9721.
-
-=item *
-
-C<Time::Local> has been upgraded from version 1.1901_01 to 1.2000.
-
-=item *
-
-C<Time::Piece> has been upgraded from version 1.15_01 to 1.20_01.
-
-=item *
-
C<Unicode::Collate> has been upgraded from version 0.52_01 to 0.73.
-Includes Unicode Collation Algorithm 18
-
-Among other things, it is now using UCA Revision 20 (based on Unicode 5.2.0) and
-supports a couple of new locales.
-
-U::C::Locale newly supports locales: ar, be, bg, de__phonebook, hu, hy, kk, mk, nso, om,
-tn, vi, hr, ig, ru, sq, se, sr, to and uk
-
-This release newly adds locales C<ja> C<ko> and C<zh> and its variants
-( C<zh__big5han>, C<zh__gb2312han>, C<zh__pinyin>, C<zh__stroke> ).
+Unicode::Collate has been updated to use Unicode 6.0.0.
-Supported UCA_Version 22 for Unicode 6.0.0.
+Unicode::Collate::Locale now supports a plethora of new locales: ar, be,
+bg, de__phonebook, hu, hy, kk, mk, nso, om, tn, vi, hr, ig, ja, ko, ru, sq,
+se, sr, to, uk, zh, zh__big5han, zh__gb2312han, zh__pinyin and zh__stroke.
The following modules have been added:
C<Unicode::Collate::CJK::Stroke> for C<zh__stroke> which makes
tailoring of CJK Unified Ideographs in the order of CLDR's stroke ordering.
-DUCET has been updated for Unicode 6.0.0 as Collate/allkeys.txt and
-the default UCA_Version is 22.
-
This also sees the switch from using the pure-perl version of this
module to the XS version.
=item *
-C<Unicode::Normalize> has been upgraded from version 1.03 to 1.10.
-
-=item *
-
C<Unicode::UCD> has been upgraded from version 0.27 to 0.32.
-Add info about named sequence alternatives.
+A new function, C<Unicode::UCD::num()>, has been added. This function
+returns the numeric value of the string passed it or C<undef> if the string
+in its entirety has no "safe" numeric value. (For more detail, and for the
+definition of "safe", see L<Unicode::UCD/num>.)
-Don't use C<CompositionExclusions.txt>.
-
-This includes a number of bug fixes:
+This upgrade also includes a number of bug fixes:
=over 4
=item *
-The CJK (Chinese-Japanese-Korean) code points U+2A700 - U+2B734
-and U+2B740 - 2B81D are now properly handled.
+The CJK (Chinese-Japanese-Korean) code points U+2A700 to U+2B734
+and U+2B740 to U+2B81D are now properly handled.
=item *
=back
-Added new function C<Unicode::UCD::num()>. This function will return the
-numeric value of the string passed it; C<undef> if the string in its
-entirety has no safe numeric value.
-
-To be safe, a string must be a single character which has a numeric
-value, or consist entirely of characters that match \d, coming from the
-same Unicode block of digits. Thus, a mix of Bengali and Western
-digits would be considered unsafe, as well as a mix of half- and
-full-width digits, but strings consisting entirely of Devanagari digits
-or of "Mathematical Bold" digits would would be safe.
-
=item *
C<version> has been upgraded from 0.82 to 0.88.
-Modify export logic for C<is_strict> and C<is_lax>.
+Due to a bug, now fixed, the C<is_strict> and C<is_lax> functions did not
+work when exported.
=item *
C<Win32> has been upgraded from version 0.39 to 0.44.
-Add several functions. (5.13.8)
-
-Corrections to names returned by C<Win32::GetOSName> and
-C<Win32::GetOSDisplayName>.
-
-=item *
-
-C<XSLoader> has been upgraded from version 0.10 to 0.11.
-
-=back
-
-=head2 Dual-life Modules and Pragmata
-
-These modules were formerly distributed only in the Perl core
-distribution, and are now dual-lifed (meaning they are now also available
-separately on CPAN):
-
-=over 4
-
-=item *
-
-C<autouse>
+This release has several new functions: C<Win32::GetSystemMetrics>,
+C<Win32::GetProductInfo>, C<Win32::GetOSDisplayName>.
-=item *
-
-C<Devel::SelfStubber>
-
-=item *
-
-C<Dumpvalue>
-
-=item *
-
-C<Env>
-
-=item *
-
-C<File::CheckTree>
-
-=item *
-
-C<I18N::Collate>
+The names returned by C<Win32::GetOSName> and C<Win32::GetOSDisplayName>
+have been corrected.
=back
=head1 Documentation
-XXX Changes to files in F<pod/> go here. Consider grouping entries by
-file and be sure to link to the appropriate page, e.g. L<perlfunc>.
-
=head2 New Documentation
-=head3 perlgpl
+=head3 L<perlgpl>
L<perlgpl> has been updated to contain GPL version 1, as is included in the
F<README> distributed with perl.
-=head3 L<perl5121delta>
+=head3 Perl 5.12.x delta files
-The Perl 5.12.1 perldelta file was added from the Perl maintenance branch
+The perldelta files for Perl 5.12.1 to 5.12.3 have been added from the
+maintenance branch: L<perl5121delta>, L<perl5122delta>, L<perl5123delta>.
=head3 L<perlpodstyle>
New style guide for POD documentation,
split mostly from the NOTES section of the pod2man man page.
-( This was added to C<v5.13.6> but was not documented with that release ).
+=head3 L<perlsource>, L<perlinterp>, L<perlhacktut>, and L<perlhacktips>
+
+See L</L<perlhack> and perlrepository revamp>, below.
=head2 Changes to Existing Documentation
-=head3 L<perlmodlib>
+=head3 L<perlmodlib> is now complete
The perlmodlib page that came with Perl 5.12.0 was missing a lot of
modules, due to a bug in the script that generates the list. This has been
fixed [perl #74332].
-=head3 Replace wrong tr/// table in perlebcdic.pod
+=head3 Replace wrong tr/// table in L<perlebcdic>
-perlebcdic.pod contains a helpful table to use in tr/// to convert
+L<perlebcdic> contains a helpful table to use in tr/// to convert
between EBCDIC and Latin1/ASCII. Unfortunately, the table was the
inverse of the one it describes, though the code that used the table
worked correctly for the specific example given.
-The table has been changed to its inverse, and the sample code changed
-to correspond, as this is easier for the person trying to follow the
-instructions since deriving the old table is somewhat more complicated.
-
-The table has also been changed to hex from octal, as that is more the norm
-these days, and the recipes in the pod altered to print out leading
-zeros to make all the values the same length, as the table that they can
-generate has them (5f26d5).
-
-=head3 Document tricks for user-defined casing
-
-perlunicode.pod now contains an explanation of how to override, mangle
-and otherwise tweak the way perl handles upper, lower and other case
-conversions on unicode data, and how to provide scoped changes to alter
-one's own code's behaviour without stomping on anybody else (71648f).
-
-=head3 Document $# and $* as removed and clarify $#array usage
-
-$# and $* were both disabled as of perl5 version 10; this release adds
-documentation to that effect, a description of the results of continuing
-to try and use them, and a note explaining that $# can also function as a
-sigil in the $#array form (7f315d2).
-
-=head3 INSTALL explicitly states the requirement for C89
-
-This was already true but it's now Officially Stated For The Record (51eec7).
-
-=head3 No longer advertise Math::TrulyRandom
-
-This module hasn't been updated since 1996 so we can't recommend it any more
-(83918a).
-
-=head3 perlfaq synchronised to upstream
-
-The FAQ has been updated to commit
-37550b8f812e591bcd0dd869d61677dac5bda92c from the perlfaq repository
-at git@github.com:briandfoy/perlfaq.git
-
-=head3 General changes
-
-=over
-
-=item *
-
-Octal character escapes in documentation now prefer a three-digit octal
-escape or the new C<\o{...}> escape as they have more consistent behavior
-in different contexts than other forms. (ce7b6f0) (d8b950d) (e1f120a)
-
-=item *
-
-Documentation now standardizes on the term 'capture group' over 'buffer'
-in regular expression documentation (c27a5cf)
-
-=back
-
-=head3 L<perlfunc>
-
-=over
-
-=item *
-
-Added cautionary note about "no VERSION" (e0de7c2)
-
-=item *
-
-Added additional notes regarding srand when forking (d460397)
-
-=back
-
-=head3 L<perlop>
-
-=over 4
-
-=item *
-
-Improved documentation of unusual character escapes (4068718, 9644846)
-
-=item *
-
-Clarified how hexadecimal escapes are interpreted, with particular
-attention to the treatment of invalid characters (9644846)
-
-=back
-
-=head3 L<perlrun>
-
-=over
-
-=item *
-
-Clarified the behavior of the C<-0NNN> switch for C<-0400> or higher (7ba31cb)
-
-=back
-
-=head3 L<perlpolicy>
-
-=over
-
-=item *
-
-Added the policy on compatibility and deprecation along with definitions of
-terms like "deprecation" (70e4a83)
-
-=back
-
-=head3 L<perlre>
-
-=over
-
-=item *
-
-Added examples of the perils of not using \g{} when there are more
-than nine back-references (9d86067)
-
-=back
-
-=head3 L<perltie>
-
-=over
-
-=item *
-
-Updated some examples for modern Perl style (67d00dd)
-
-=back
-
-=head3 L<perldiag>
-
-=over 4
-
-=item *
-
-The following existing diagnostics are now documented:
-
-=over 4
-
-=item *
-
-L<Ambiguous use of %c resolved as operator %c|perldiag/"Ambiguous use of %c resolved as operator %c">
-
-=item *
-
-L<Ambiguous use of %c{%s} resolved to %c%s|perldiag/"Ambiguous use of %c{%s} resolved to %c%s">
-
-=item *
-
-L<Ambiguous use of %c{%s%s} resolved to %c%s%s|perldiag/"Ambiguous use of %c{%s%s} resolved to %c%s%s">
-
-=item *
-
-L<Ambiguous use of -%s resolved as -&%s()|perldiag/"Ambiguous use of -%s resolved as -&%s()">
-
-=item *
-
-L<Invalid strict version format (%s)|perldiag/"Invalid strict version format (%s)">
-
-=item *
-
-L<Invalid version format (%s)|perldiag/"Invalid version format (%s)">
-
-=item *
-
-L<Invalid version object|perldiag/"Invalid version object">
-
-=back
-
-=back
-
-=head3 L<perlport>
-
-=over 4
-
-=item *
-
-Documented a L<limitation|perlport/alarm> of L<alarm()|perlfunc/"alarm SECONDS">
-on Win32.
-
-=back
-
-=head3 L<perlre>
-
-=over 4
-
-=item *
-
-Minor fix to a multiple scalar match example.
-
-=back
-
-=head3 L<perlapi>
-
-=over 4
-
-=item *
+The table has been changed to its inverse, and the sample code changed
+to correspond, as this is easier for the person trying to follow the
+instructions since deriving the old table is somewhat more complicated.
-Many of the optree construction functions are now documented.
+The table has also been changed to hex from octal, as that is more the norm
+these days, and the recipes in the pod altered to print out leading
+zeros to make all the values the same length.
-=back
+=head3 Tricks for user-defined casing
-=head3 L<perlbook>
+L<perlunicode> now contains an explanation of how to override, mangle
+and otherwise tweak the way perl handles upper-, lower- and other-case
+conversions on Unicode data, and how to provide scoped changes to alter
+one's own code's behaviour without stomping on anybody else.
-=over 4
+=head3 INSTALL explicitly states the requirement for C89
-=item *
+This was already true but it's now Officially Stated For The Record.
-Expanded to cover many more popular books.
+=head3 Explanation of C<\xI<HH>> and C<\oI<OOO>> escapes
-=back
+L<perlop> has been updated with more detailed explanation of these two
+character escapes.
-=head3 L<perlfaq>
+=head3 C<-0I<NNN>> switch
-=over 4
+In L<perlrun>, the behavior of the C<-0NNN> switch for C<-0400> or higher
+has been clarified.
-=item *
+=head3 Deprecation policy
-L<perlfaq>, L<perlfaq2>, L<perlfaq4>, L<perlfaq5>, L<perlfaq6>, L<perlfaq8>, and
-L<perlfaq9> have seen various updates and modernizations.
+L<perlpolicy> now contains the policy on compatibility and deprecation
+along with definitions of terms like "deprecation"
-=back
+=head3 New descriptions in L<perldiag>
-=head3 L<perlapi>
+The following existing diagnostics are now documented:
=over 4
=item *
-The documentation for the C<SvTRUE> macro was simply wrong in stating that
-get-magic is not processed. It has been corrected.
-
-=back
+L<Ambiguous use of %c resolved as operator %c|perldiag/"Ambiguous use of %c resolved as operator %c">
-=head3 L<perlvar>
+=item *
-L<perlvar> reorders the variables and groups them by topic. Each variable
-introduced after Perl 5.000 notes the first version in which it is
-available. L<perlvar> also has a new section for deprecated variables to
-note when they were removed.
+L<Ambiguous use of %c{%s} resolved to %c%s|perldiag/"Ambiguous use of %c{%s} resolved to %c%s">
-=head3 blah blah blah
+=item *
-Array and hash slices in scalar context are now documented in L<perldata>.
+L<Ambiguous use of %c{%s%s} resolved to %c%s%s|perldiag/"Ambiguous use of %c{%s%s} resolved to %c%s%s">
-=head3 blah blah blah
+=item *
-L<perlform> and L<perllocale> have been corrected to state that
-C<use locale> affects formats.
+L<Ambiguous use of -%s resolved as -&%s()|perldiag/"Ambiguous use of -%s resolved as -&%s()">
-=head3 All documentation
+=item *
-=over
+L<Invalid strict version format (%s)|perldiag/"Invalid strict version format (%s)">
=item *
-Numerous POD warnings were fixed.
+L<Invalid version format (%s)|perldiag/"Invalid version format (%s)">
=item *
-Many, many spelling errors and typographical mistakes were corrected throughout Perl's core.
+L<Invalid version object|perldiag/"Invalid version object">
=back
-=head3 C<perlhack>
+=head3 L<perlbook>
-=over 4
+L<perlbook> has been expanded to cover many more popular books.
-=item *
+=head3 C<SvTRUE> macro
-C<perlhack> was extensively reorganized.
+The documentation for the C<SvTRUE> macro in
+L<perlapi> was simply wrong in stating that
+get-magic is not processed. It has been corrected.
-=back
+=head3 L<perlvar> revamp
-=head3 C<perlfunc>
+L<perlvar> reorders the variables and groups them by topic. Each variable
+introduced after Perl 5.000 notes the first version in which it is
+available. L<perlvar> also has a new section for deprecated variables to
+note when they were removed.
-=over 4
+=head3 Array and hash slices in scalar context
-=item *
+These are now documented in L<perldata>.
-It has now been documented that C<ord> returns 0 for an empty string.
+=head3 C<use locale> and formats
-=back
+L<perlform> and L<perllocale> have been corrected to state that
+C<use locale> affects formats.
=head3 L<overload>
-=over 4
-
-=item *
-
L<overload>'s documentation has practically undergone a rewrite. It
is now much more straightforward and clear.
-=back
-
-=head3 L<perlhack> and perlrepository
-
-=over 4
-
-=item *
+=head3 L<perlhack> and perlrepository revamp
The L<perlhack> and perlrepository documents have been heavily edited and
split up into several new documents.
is just a how-to on using git with the Perl source code. Any other content
that used to be in perlrepository has been moved to perlhack.
-=back
-
-=head3 L<perlfunc>
-
-=over 4
-
-=item *
-
-The documentation for the C<map> function now contains more examples,
-see B<perldoc -f map> (f947627)
-
-=back
-
-=head3 L<perlfaq4>
-
-=over 4
-
-=item *
+=head3 Time::Piece examples
Examples in L<perlfaq4> have been updated to show the use of
-L<Time::Piece>. (9243591)
-
-=back
-
-=head3 Miscellaneous
-
-=over 4
-
-=item *
-
-Many POD related RT bugs and other issues which are too numerous to
-enumerate have been solved by Michael Stevens.
-
-=back
+L<Time::Piece>.
=head1 Diagnostics
=head2 New Diagnostics
+=head3 New Errors
+
=over
-=item Parsing code internal error (%s)
+=item Closure prototype called
-New fatal error produced when parsing code supplied by an extension violated the
-parser's API in a detectable way.
+This error occurs when a subroutine reference passed to an attribute
+handler is called, if the subroutine is a closure [perl #68560].
-=item Use of qw(...) as parentheses is deprecated
+=item Insecure user-defined property %s
-See L</"Use of qw(...) as parentheses"> for details.
+Perl detected tainted data when trying to compile a regular
+expression that contains a call to a user-defined character property
+function, i.e. C<\p{IsFoo}> or C<\p{InFoo}>.
+See L<perlunicode/User-Defined Character Properties> and L<perlsec>.
-=item Using !~ with %s doesn't make sense
+=item panic: gp_free failed to free glob pointer - something is repeatedly re-creating entries
-This message was actually added in
-5.13.2, but was omitted from perldelta. It now applies also to the C<y///>
-operator, and has been documented.
+This new error is triggered if a destructor called on an object in a
+typeglob that is being freed creates a new typeglob entry containing an
+object with a destructor that creates a new entry containing an object....
-=item Closure prototype called
+=item Parsing code internal error (%s)
-There is a new "Closure prototype called" error [perl #68560].
+This new fatal error is produced when parsing
+code supplied by an extension violates the
+parser's API in a detectable way.
-=item Operation "%s" returns its argument for ...
+=item refcnt: fd %d%s
-Performing an operation requiring Unicode semantics (such as case-folding)
-on a Unicode surrogate or a non-Unicode character now triggers a warning:
-'Operation "%s" returns its argument for ...'.
+This new error only occurs if a internal consistency check fails when a
+pipe is about to be closed.
-=item "\b{" is deprecated; use "\b\{" instead
+=item Regexp modifier "/%c" may not appear twice
-=item "\B{" is deprecated; use "\B\{" instead
+The regular expression pattern has one of the
+mutually exclusive modifiers repeated.
-Use of an unescaped "{" immediately following a C<\b> or C<\B> is now
-deprecated so as to reserve its use for Perl itself in a future release.
+=item Regexp modifiers "/%c" and "/%c" are mutually exclusive
-=item regcomp: Add warning if \p is used under locale. (fb2e24c)
+The regular expression pattern has more than one of the mutually
+exclusive modifiers.
-C<\p> implies Unicode matching rules, which are likely going to be
-different than the locale's.
+=item Using !~ with %s doesn't make sense
-=item panic: gp_free failed to free glob pointer - something is repeatedly re-creating entries
+This error occurs when C<!~> is used with C<s///r> or C<y///r>.
-This new error is triggered if a destructor called on an object in a
-typeglob that is being freed creates a new typeglob entry containing an
-object with a destructor that creates a new entry containing an object....
+=back
-=item refcnt: fd %d%s
+=head3 New Warnings
-This new error only occurs if a internal consistency check fails when a
-pipe is about to be closed.
+=over
-=item Regexp modifier "/%c" may not appear twice
+=item "\b{" is deprecated; use "\b\{" instead
-(F syntax) The regular expression pattern had one of the mutually exclusive
-modifiers repeated. Remove all but one of the occurrences.
+=item "\B{" is deprecated; use "\B\{" instead
-=item Regexp modifiers "/%c" and "/%c" are mutually exclusive
+Use of an unescaped "{" immediately following a C<\b> or C<\B> is now
+deprecated so as to reserve its use for Perl itself in a future release.
-(F syntax) The regular expression pattern had more than one of the mutually
-exclusive modifiers. Retain only the modifier that is supposed to be there.
+=item Operation "%s" returns its argument for ...
-=item Insecure user-defined property %s
+Performing an operation requiring Unicode semantics (such as case-folding)
+on a Unicode surrogate or a non-Unicode character now triggers a warning:
+'Operation "%s" returns its argument for ...'.
-(F) Perl detected tainted data when trying to compile a regular
-expression that contains a call to a user-defined character property
-function, i.e. C<\p{IsFoo}> or C<\p{InFoo}>.
-See L<perlunicode/User-Defined Character Properties> and L<perlsec>.
+=item Use of qw(...) as parentheses is deprecated
+
+See L</"Use of qw(...) as parentheses">, above, for details.
=back
=item *
The 'Layer does not match this perl' error message has been replaced with
-these more helpful messages:
+these more helpful messages [perl #73754]:
=over 4
=back
-[perl #73754]
-
=item *
The "Found = in conditional" warning that is emitted when a constant is
=item *
-The warning message about regex unrecognized escapes passed through is
-changed to include any literal '{' following the 2-char escape. e.g.,
-"\q{" will include the { in the message as part of the escape
-(216bfc0).
-
-=item *
-
-C<binmode $fh, ':scalar'> no longer warns (8250589)
-
-Perl will now no longer produce this warning:
-
- $ perl -we 'open my $f, ">", \my $x; binmode $f, "scalar"'
- Use of uninitialized value in binmode at -e line 1.
+The warning message about unrecognized regular expression escapes passed
+through has been changed to include any literal '{' following the
+two-character escape. E.g., "\q{" is now emitted instead of "\q".
=back
=head1 Utility Changes
-=head3 L<perldb>
-
-=over
-
-=item *
-
-The remote terminal works after forking and spawns new sessions - one
-for each forked process (11653f7)
-
-=item *
-
-Uses the less pager path from Config instead of searching for it (bf320d6)
-
-=back
-
-=head3 L<h2ph>
+=head3 L<perlbug>
=over 4
=item *
-The use of a deprecated C<goto> construct has been removed [perl #74404].
-
-=back
-
-=head3 L<ptargrep>
-
-=over 4
+L<perlbug> now looks in the EMAIL environment variable for a return address
+if the REPLY-TO and REPLYTO variables are empty.
=item *
-L<ptargrep> is a utility to apply pattern matching to the contents of files
-in a tar archive. It comes with C<Archive::Tar>.
-
-=back
-
-=head3 C<perlbug>
-
-=over 4
+L<perlbug> did not previously generate a From: header, potentially
+resulting in dropped mail. Now it does include that header.
=item *
-C<perlbug> now looks in the EMAIL environment variable for a return address
-if the REPLY-TO and REPLYTO variables are empty.
-
-=item *
+The user's address is now used as the return-path.
-C<perlbug> did not previously generate a From: header, potentially
-resulting in dropped mail. Now it does include that header.
+Many systems these days don't have a valid Internet domain name and
+perlbug@perl.org does not accept email with a return-path that does
+not resolve. So the user's address is now passed to sendmail so it's
+less likely to get stuck in a mail queue somewhere [perl #82996].
=back
-=head3 C<buildtoc>
+=head3 L<perl5db.pl>
-=over 4
+=over
=item *
-F<pod/buildtoc> has been modernized and can now be used to test the
-well-formedness of F<pod/perltoc.pod> automatically.
+The remote terminal works after forking and spawns new sessions - one
+for each forked process.
=back
-=head3 L<perlbug>
+=head3 L<ptargrep>
=over 4
=item *
-[perl #82996] Use the user's from address as return-path in perlbug
-
-Many systems these days don't have a valid Internet domain name and
-perlbug@perl.org does not accept email with a return-path that does
-not resolve. Therefore pass the user's address to sendmail so it's
-less likely to get stuck in a mail queue somewhere. (019cfd2)
+L<ptargrep> is a new utility to apply pattern matching to the contents of
+files in a tar archive. It comes with C<Archive::Tar>.
=back
=head1 Configuration and Compilation
+See also L</"Naming fixes in Policy_sh.SH may invalidate Policy.sh">,
+above.
+
=over 4
=item *
=head1 Internal Changes
-=head2 New APIs
-
-=head2 CLONE_PARAMS structure added to ease correct thread creation
-
-Modules that create threads should now create C<CLONE_PARAMS> structures
-by calling the new function C<Perl_clone_params_new()>, and free them with
-C<Perl_clone_params_del()>. This will ensure compatibility with any future
-changes to the internals of the C<CLONE_PARAMS> structure layout, and that
-it is correctly allocated and initialised.
-
-=head2 API function to parse statements
-
-The C<parse_fullstmt> function has been added to allow parsing of a single
-complete Perl statement. See L<perlapi> for details.
-
-=head2 API functions for accessing the runtime hinthash
-
-A new C API for introspecting the hinthash C<%^H> at runtime has been added.
-See C<cop_hints_2hv>, C<cop_hints_fetchpvn>, C<cop_hints_fetchpvs>,
-C<cop_hints_fetchsv>, and C<hv_copy_hints_hv> in L<perlapi> for details.
-
-=head2 C interface to C<caller()>
-
-The C<caller_cx> function has been added as an XSUB-writer's equivalent of
-C<caller()>. See L<perlapi> for details.
-
-=head2 Custom per-subroutine check hooks
-
-XS code in an extension module can now annotate a subroutine (whether
-implemented in XS or in Perl) so that nominated XS code will be called
-at compile time (specifically as part of op checking) to change the op
-tree of that subroutine. The compile-time check function (supplied by
-the extension module) can implement argument processing that can't be
-expressed as a prototype, generate customised compile-time warnings,
-perform constant folding for a pure function, inline a subroutine
-consisting of sufficiently simple ops, replace the whole call with a
-custom op, and so on. This was previously all possible by hooking the
-C<entersub> op checker, but the new mechanism makes it easy to tie the
-hook to a specific subroutine. See L<perlapi/cv_set_call_checker>.
-
-To help in writing custom check hooks, several subtasks within standard
-C<entersub> op checking have been separated out and exposed in the API.
-
-=head2 Improved support for custom OPs
-
-Custom ops can now be registered with the new C<custom_op_register> C
-function and the C<XOP> structure. This will make it easier to add new
-properties of custom ops in the future. Two new properties have been added
-already, C<xop_class> and C<xop_peep>.
-
-C<xop_class> is one of the OA_*OP constants, and allows L<B> and other
-introspection mechanisms to work with custom ops that aren't BASEOPs.
-C<xop_peep> is a pointer to a function that will be called for ops of this
-type from C<Perl_rpeep>.
-
-See L<perlguts/Custom Operators> and L<perlapi/Custom Operators> for more
-detail.
-
-The old C<PL_custom_op_names>/C<PL_custom_op_descs> interface is still
-supported but discouraged.
-
-=head2 Return value of C<delete $+{...}>
-
-Custom regular expression engines can now determine the return value of
-C<delete> on an entry of C<%+> or C<%->.
-
-XXX Mention the actual API.
-
-=head2 Changes to existing APIs
-
-XXX This probably contains also internal changes unrelated to APIs. It
-needs to be sorted out. Maybe we also need an ‘Other Changes’ or ‘Really
-Internal Changes’ section.
+See also L</New C APIs>, L</C API Changes> and L</Deprecated C APIs>, above.
=over 4
=item *
+C<binmode $fh, ':scalar'> no longer warns (8250589)
+
+Perl will now no longer produce this warning:
+
+ $ perl -we 'open my $f, ">", \my $x; binmode $f, "scalar"'
+ Use of uninitialized value in binmode at -e line 1.
+
+=item *
+
C<when(scalar){...}> no longer crashes, but produces a syntax error
[perl #74114].
=item *
-An erroneous regular expression engine optimization that caused regex verbs like
+An erroneous regular expression engine optimisation that caused regex verbs like
C<*COMMIT> to sometimes be ignored has been removed.
=item *
https://perl5.git.perl.org / perl5.git / blobdiff