=head1 NAME
-[ 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.13.0
+perldelta5130 - what is new for perl v5.13.0
=head1 DESCRIPTION
-This document describes differences between the 5.13.0 release and
-the 5.13.0 elease.
+This document describes differences between the 5.12.0 release and the
+5.13.0 release.
If you are upgrading from an earlier release such as 5.10.0, first read
L<perl5120delta>, which describes differences between 5.10.0 and
5.12.0.
-=head1 Notice
-
-XXX Any important notices here
-
-=head1 Incompatible Changes
-
-XXX For a release on a stable branch, this section aspires to be:
-
- There are no changes intentionally incompatible with 5.XXX.XXX. If any
- exist, they are bugs and reports are welcome.
-
-
=head1 Core Enhancements
-Signal dispatch has been moved from the runloop into control ops. This should
-give a few percent speed increase, and eliminates almost all of the speed
-penalty caused by the introduction of "safe signals" in 5.8.0. Signals should
-still be dispatched within the same statement as they were previously - if
-this is not the case, or it is possible to create uninterruptable loops, this
-is a bug, and reports are encouraged of how to recreate such issues.
+=head2 "safe signals" optimization
-=head1 New Platforms
+Signal dispatch has been moved from the runloop into control ops. This
+should give a few percent speed increase, and eliminates almost all of
+the speed penalty caused by the introduction of "safe signals" in
+5.8.0. Signals should still be dispatched within the same statement as
+they were previously - if this is not the case, or it is possible to
+create uninterruptable loops, this is a bug, and reports are encouraged
+of how to recreate such issues.
-XXX List any platforms that this version of perl compiles on, that previous
-versions did not. These will either be enabled by new files in the F<hints/>
-directories, or new subdirectories and F<README> files at the top level of the
-source tree.
+=head2 Assignment to C<$0> sets the legacy process name with C<prctl()> on Linux
-=head1 Modules and Pragmata
+On Linux the legacy process name will be set with L<prctl(2)>, in
+addition to altering the POSIX name via C<argv[0]> as perl has done
+since version 4.000. Now system utilities that read the legacy process
+name such as ps, top and killall will recognize the name you set when
+assigning to C<$0>. The string you supply will be cut off at 16 bytes,
+this is a limitation imposed by Linux.
-XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
-go here. If Module::CoreList is updated, generate an initial draft of the
-following sections using F<Porting/corelist-perldelta.pl>, which prints stub
-entries to STDOUT. Results can be pasted in place of the '=head2' entries
-below. A paragraph summary for important changes should then be added by hand.
-In an ideal world, dual-life modules would have a F<Changes> file that could be
-cribbed.
+=head2 Optimization of shift; and pop; calls without arguments
-=head2 New Modules and Pragmata
+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.
-=head2 Pragmata Changes
+=head1 Modules and Pragmata
=head2 Updated Modules
-=head2 Removed Modules and Pragmata
-
-=head1 Utility Changes
-
-XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
-here. Most of these are built within the directories F<utils> and F<x2p>.
-
-=over 4
-
-=item F<XXX>
-
-XXX
-
-=back
-
-=head1 New Documentation
-
-XXX Changes which create B<new> files in F<pod/> go here.
-
=over 4
-=item L<XXX>
-
-XXX
+=item CGI
-=back
+Updated to version 3.49.
-=head1 Changes to Existing Documentation
+=item Data::Dumper
-XXX Changes which significantly change existing files in F<pod/> go here.
-Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
+Updated to version 2.126.
+=item MIME::Base64
-=head1 Performance Enhancements
+Updated to 3.09.
-XXX Changes which enhance performance without changing behaviour go here. There
-may well be none in a stable release.
+=item threads
-=over 4
+Updated to version 1.77
-=item *
+=item threads-shared
-XXX
+Updated to version 1.33
=back
=head1 Installation and Configuration Improvements
-XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
-go here.
-
-=head2 Configuration improvements
-
-XXX
-
-=head2 Compilation improvements
-
-XXX
-
=head2 Platform Specific Changes
=over 4
-=item XXX-some-platform
+=item AIX
-XXX
+Allow building on AIX 4.2.
=back
-=head1 Selected Bug Fixes
-
-XXX Important bug fixes in the core language are summarised here.
-Bug fixes in files in F<ext/> and F<lib/> are best summarised in
-L</Modules and Pragmata>.
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head1 New or Changed Diagnostics
-
-XXX New or changed warnings emitted by the core's C<C> code go here.
-
-=over 4
-
-=item C<XXX>
-
-XXX
-
-=back
-
-=head1 Changed Internals
-
-XXX Changes which affect the interface available to C<XS> code go here.
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head1 New Tests
-
-XXX Changes which create B<new> files in F<t/> go here. Changes to
-existing files in F<t/> aren't worth summarising, although the bugs that
-they represent may be.
-
-=over 4
-
-=item F<XXX>
-
-XXX
-
-=back
-
-=head1 Known Problems
-
-XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
-tests that had to be C<TODO>ed for the release would be noted here, unless
-they were specific to a particular platform (see below).
-
-This is a list of some significant unfixed bugs, which are regressions
-from either 5.XXX.XXX or 5.XXX.XXX.
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head1 Deprecations
-
-XXX Add any new known deprecations here.
-
-The following items are now deprecated.
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head1 Platform Specific Notes
-
-XXX Any changes specific to a particular platform. VMS and Win32 are the usual
-stars here. It's probably best to group changes under the same section layout
-as the main perldelta
-
-=head1 Obituary
-
-XXX If any significant core contributor has died, we've added a short obituary
-here.
-
=head1 Acknowledgements
-XXX The list of people to thank goes here.
+Perl 5.13.0 represents eight days of development since Perl 5.12.0 and
+contains 3,766 lines of changes across 151 files from 29 authors and
+committers.
+
+Thank you to the following for contributing to this release:
+Ævar Arnfjörð Bjarmason, Alex Vandiver, Chris Williams, chromatic,
+Craig A. Berry, David Golden, David Mitchell, Eric Brine, Father
+Chrysostomos, Florian Ragwitz, Frank Wiegand, Gisle Aas, H.Merijn
+Brand, Hugo van der Sanden, Jesse Vincent, Josh ben Jore, Karl
+Williamson, Leon Brocard, Michael G Schwern, Michael G. Schwern, Nga
+Tang Chan, Nicholas Clark, Niko Tyni, Rafael Garcia-Suarez, Ricardo
+Signes, Robin Barker, Slaven Rezic, Steffen Mueller, Zefram.
=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 http://rt.perl.org/perlbug/ . There may also be
+recently posted to the comp.lang.perl.misc newsgroup and the perl bug
+database at http://rt.perl.org/perlbug/ . There may also be
information at http://www.perl.org/ , the Perl Home Page.
If you believe you have an unreported bug, please run the B<perlbug>
-program included with your release. Be sure to trim your bug down
-to a tiny but sufficient test case. Your bug report, along with the
-output of C<perl -V>, will be sent off to perlbug@perl.org to be
-analysed by the Perl porting team.
+program included with your release. Be sure to trim your bug down to a
+tiny but sufficient test case. Your bug report, along with the output
+of C<perl -V>, will be sent off to perlbug@perl.org to be analysed by
+the Perl porting team.
If the bug you are reporting has security implications, which make it
-inappropriate to send to a publicly archived mailing list, then please send
-it to perl5-security-report@perl.org. This points to a closed subscription
-unarchived mailing list, which includes all the core committers, who be able
-to help assess the impact of issues, figure out a resolution, and help
-co-ordinate the release of patches to mitigate or fix the problem across all
-platforms on which Perl is supported. Please only use this address for
-security issues in the Perl core, not for modules independently
-distributed on CPAN.
+inappropriate to send to a publicly archived mailing list, then please
+send it to perl5-security-report@perl.org. This points to a closed
+subscription unarchived mailing list, which includes all the core
+committers, who be able to help assess the impact of issues, figure out
+a resolution, and help co-ordinate the release of patches to mitigate
+or fix the problem across all platforms on which Perl is supported.
+Please only use this address for security issues in the Perl core, not
+for modules independently distributed on CPAN.
=head1 SEE ALSO
-The F<Changes> file for an explanation of how to view exhaustive details
-on what changed.
+The F<Changes> file for an explanation of how to view exhaustive
+details on what changed.
The F<INSTALL> file for how to build Perl.
https://perl5.git.perl.org / perl5.git / blobdiff