[ this is a template for a new perldelta file. Any text flagged as XXX needs
to be processed before release. ]
-perldelta - what is new for perl v5.25.2
+perldelta - what is new for perl v5.25.3
=head1 DESCRIPTION
-This document describes differences between the 5.25.1 release and the 5.25.2
+This document describes differences between the 5.25.2 release and the 5.25.3
release.
-If you are upgrading from an earlier release such as 5.25.0, first read
-L<perl5251delta>, which describes differences between 5.25.0 and 5.25.1.
+If you are upgrading from an earlier release such as 5.25.1, first read
+L<perl5252delta>, which describes differences between 5.25.1 and 5.25.2.
=head1 Notice
[ List each enhancement as a =head2 entry ]
-=head2 Perl can now do default collation in UTF-8 locales on platforms
-that support it
+=head2 Unicode 9.0 is now supported
-Some platforms natively do a reasonable job of collating and sorting in
-UTF-8 locales. Perl now works with those. For portability and full
-control, L<Unicode::Collate> is still recommended, but now you may
-not need to do anything special to get good-enough results, depending on
-your application. See
-L<perllocale/Category C<LC_COLLATE>: Collation: Text Comparisons and Sorting>
-
-=head2 Better locale collation of strings containing embedded C<NUL>
-characters
-
-In locales that have multi-level character weights, these are now
-ignored at the higher priority ones. There are still some gotchas in
-some strings, though. See
-L<perllocale/Collation of strings containing embedded C<NUL> characters>.
-
-=head2 Lexical subroutines are no longer experimental
-
-Using the C<lexical_subs> feature no longer emits a warning. Existing code that disables the C<experimental::lexical_subs> warning category that the
-feature previously used will continue to work. The C<lexical_subs> feature
-has no effect; all Perl code can use lexical subroutines, regardless of
-what feature declarations are in scope.
-
-=head2 C<CORE> subroutines for hash and array functions callable via
-reference
-
-The hash and array functions in the C<CORE> namespace--C<keys>, C<each>,
-C<values>, C<push>, C<pop>, C<shift>, C<unshift> and C<splice>--, can now
-be called with ampersand syntax (C<&CORE::keys(\%hash>) and via reference
-(C<<my $k = \&CORE::keys; $k->(\%hash) >>). Previously they could only be
-used when inlined.
+A list of changes is at
+L<http://www.unicode.org/versions/Unicode9.0.0/>. Modules that are
+shipped with core Perl but not maintained by p5p do not necessarily
+support Unicode 9.0. L<Unicode::Normalize> does work on 9.0.
=head1 Security
[ List each security issue as a =head2 entry ]
-=head2 C<-Di> switch is now required for PerlIO debugging output
-
-Previously PerlIO debugging output would be sent to the file specified
-by the C<PERLIO_DEBUG> environment variable if perl wasn't running
-setuid and the C<-T> or C<-t> switches hadn't been parsed yet.
-
-If perl performed output at a point where it hadn't yet parsed its
-switches this could result in perl creating or overwriting the file
-named by C<PERLIO_DEBUG> even when the C<-T> switch had been supplied.
-
-Perl now requires the C<-Di> switch to produce PerlIO debugging
-output. By default this is written to C<stderr>, but can optionally
-be redirected to a file by setting the C<PERLIO_DEBUG> environment
-variable.
-
-If perl is running setuid or the C<-T> switch has supplied
-C<PERLIO_DEBUG> is ignored and the debugging output is sent to
-C<stderr> as for any other C<-D> switch.
-
=head1 Incompatible Changes
XXX For a release on a stable branch, this section aspires to be:
[ List each incompatible change as a =head2 entry ]
-=head2 C<keys> returned from an lvalue subroutine
-
-C<keys> returned from an lvalue subroutine can no longer be assigned
-to in list context.
-
- sub foo : lvalue { keys(%INC) }
- (foo) = 3; # death
- sub bar : lvalue { keys(@_) }
- (bar) = 3; # also an error
-
-This makes the lvalue sub case consistent with C<(keys %hash) = ...> and
-C<(keys @_) = ...>, which are also errors. [perl #128187]
-
=head1 Deprecations
XXX Any deprecated features, syntax, modules etc. should be listed here.
=item *
-L<XXX> has been upgraded from version A.xx to B.yy.
+L<Module::CoreList> has been upgraded from version 5.20160620 to 5.20160720.
=item *
-L<Module::CoreList> has been upgraded from 5.20160520 to 5.20160620.
+L<XXX> has been upgraded from version A.xx to B.yy.
=back
=back
-=head3 L<perllocale>
-
-=over 4
-
-=item *
-
-Document NUL collation handling.
-
-=back
-
-=head3 L<perlmodlib>
-
-=over 4
-
-=item *
-
-Updated the mirror list
-
-=back
-
=head1 Diagnostics
The following additions or changes have been made to diagnostic output,
=item *
-L<Version control conflict marker|perldiag/"Version control conflict marker">
-
-(F) The parser found a line starting with C<E<lt><<<<<<>,
-C<E<gt>E<gt>E<gt>E<gt>E<gt>E<gt>E<gt>>, or C<=======>. These may be left by a
-version control system to mark conflicts after a failed merge operation.
-
-=item *
-
-L<%s: command not found|perldiag/"%s: command not found">
-
-(A) You've accidentally run your script through B<bash> or another shell
-instead of Perl. Check the #! line, or manually feed your script into
-Perl yourself. The #! line at the top of your file could look like
-
- #!/usr/bin/perl
-
-=item *
-
-L<%s: command not found: %s|perldiag/"%s: command not found: %s">
-
-(A) You've accidentally run your script through B<zsh> or another shell
-instead of Perl. Check the #! line, or manually feed your script into
-Perl yourself. The #! line at the top of your file could look like
-
- #!/usr/bin/perl
-
-=item *
-
-L<Unescaped left brace in regex is deprecated here, passed through in regex; marked by S<<-- HERE> in mE<sol>%sE<sol>|perldiag/"Unescaped left brace in regex is deprecated here, passed through in regex; marked by S<<-- HERE> in m/%s/">
-
-Unescaped left braces are already illegal in some contexts in regular
-expression patterns, but, due to an oversight, no deprecation warning
-was raised in other contexts where they are intended to become illegal.
-This warning is now raised in these contexts.
+XXX L<message|perldiag/"message">
=back
=item *
-L<Unescaped left brace in regex is illegal here in regex; marked by S<<-- HERE> in mE<sol>%sE<sol>|perldiag/"Unescaped left brace in regex is illegal here in regex; marked by S<<-- HERE> in m/%s/">
-
-The word "here" has been added to the message that was raised in
-v5.25.1. This is to indicate that there are contexts in which unescaped
-left braces are not (yet) illegal.
+XXX Describe change here
=back
=item *
-F<make_ext.pl> no longer updates a module's F<pm_to_blib> file when no
-files require updates. This could cause dependencies, F<perlmain.c>
-in particular, to be rebuilt unnecessarily. [perl #126710]
+XXX
=back
=item *
-Perl no longer panics when switching into some locales on machines with
-buggy C<strxfrm()> implementations in their libc. [perl #121734]
+XXX
=back
=item *
-C< until ($x = 1) { ... } > and C< ... until $x = 1 > now properly
-warn when syntax warnings are enabled. [perl #127333]
-
-=item *
-
-socket() now leaves the error code returned by the system in C<$!> on
-failure. [perl #128316]
-
-=item *
-
-Assignment variants of any bitwise ops under the C<bitwise> feature would
-crash if the left-hand side was an array or hash. [perl #128204]
-
-=item *
-
-C<require> followed by a single colon (as in C<foo() ? require : ...> is
-now parsed correctly as C<require> with implicit $_, rather than
-C<require "">. [perl #128307]
-
-=item *
-
-Scalar C<keys %hash> can now be assigned to consistently in all scalar
-lvalue contexts. Previously it worked for some contexts but not others.
-
-=item *
-
-List assignment to C<vec> or C<substr> with an array or hash for its first
-argument used to result in crashes or "Can't coerce" error messages at run
-time, unlike scalar assignment, which would give an error at compile time.
-List assignment now gives a compile-time error, too. [perl #128260]
+XXX
=back
XXX Generate this with:
- perl Porting/acknowledgements.pl v5.25.1..HEAD
+ perl Porting/acknowledgements.pl v5.25.2..HEAD
=head1 Reporting Bugs
-If you find what you think is a bug, you might check the articles recently
-posted to the comp.lang.perl.misc newsgroup and the perl bug database at
-L<https://rt.perl.org/> . There may also be information at
+If you find what you think is a bug, you might check the perl bug database
+at L<https://rt.perl.org/> . There may also be information at
L<http://www.perl.org/> , the Perl Home Page.
If you believe you have an unreported bug, please run the L<perlbug> program
https://perl5.git.perl.org / perl5.git / blobdiff