5 perldelta5130 - what is new for perl v5.13.0
9 This document describes differences between the 5.12.0 release and the
12 If you are upgrading from an earlier release such as 5.10.0, first read
13 L<perl5120delta>, which describes differences between 5.10.0 and
16 =head1 Core Enhancements
18 =head2 "safe signals" optimization
20 Signal dispatch has been moved from the runloop into control ops. This
21 should give a few percent speed increase, and eliminates almost all of
22 the speed penalty caused by the introduction of "safe signals" in
23 5.8.0. Signals should still be dispatched within the same statement as
24 they were previously - if this is not the case, or it is possible to
25 create uninterruptable loops, this is a bug, and reports are encouraged
26 of how to recreate such issues.
28 =head2 Assignment to C<$0> sets the legacy process name with C<prctl()> on Linux
30 On Linux the legacy process name will be set with L<prctl(2)>, in
31 addition to altering the POSIX name via C<argv[0]> as perl has done
32 since version 4.000. Now system utilities that read the legacy process
33 name such as ps, top and killall will recognize the name you set when
34 assigning to C<$0>. The string you supply will be cut off at 16 bytes,
35 this is a limitation imposed by Linux.
37 =head1 Modules and Pragmata
39 =head2 Updated Modules
45 Updated to version 3.49.
49 Updated to version 2.126.
57 Updated to version 1.77
61 Updated to version 1.33
65 =head1 Installation and Configuration Improvements
67 =head2 Platform Specific Changes
73 Allow building on AIX 4.2.
77 =head1 Acknowledgements
79 Perl 5.13.0 represents eight days of development since Perl 5.12.0 and
80 contains 3,766 lines of changes across 151 files from 29 authors and
83 Thank you to the following for contributing to this release:
85 Ævar Arnfjörð Bjarmason, Alex Vandiver, Chris Williams, chromatic,
86 Craig A. Berry, David Golden, David Mitchell, Eric Brine, Father
87 Chrysostomos, Florian Ragwitz, Frank Wiegand, Gisle Aas, H.Merijn
88 Brand, Hugo van der Sanden, Jesse Vincent, Josh ben Jore, Karl
89 Williamson, Leon Brocard, Michael G Schwern, Michael G. Schwern, Nga
90 Tang Chan, Nicholas Clark, Niko Tyni, Rafael Garcia-Suarez, Ricardo
91 Signes, Robin Barker, Slaven Rezic, Steffen Mueller, Zefram.
95 If you find what you think is a bug, you might check the articles
96 recently posted to the comp.lang.perl.misc newsgroup and the perl bug
97 database at http://rt.perl.org/perlbug/ . There may also be
98 information at http://www.perl.org/ , the Perl Home Page.
100 If you believe you have an unreported bug, please run the B<perlbug>
101 program included with your release. Be sure to trim your bug down to a
102 tiny but sufficient test case. Your bug report, along with the output
103 of C<perl -V>, will be sent off to perlbug@perl.org to be analysed by
104 the Perl porting team.
106 If the bug you are reporting has security implications, which make it
107 inappropriate to send to a publicly archived mailing list, then please
108 send it to perl5-security-report@perl.org. This points to a closed
109 subscription unarchived mailing list, which includes all the core
110 committers, who be able to help assess the impact of issues, figure out
111 a resolution, and help co-ordinate the release of patches to mitigate
112 or fix the problem across all platforms on which Perl is supported.
113 Please only use this address for security issues in the Perl core, not
114 for modules independently distributed on CPAN.
118 The F<Changes> file for an explanation of how to view exhaustive
119 details on what changed.
121 The F<INSTALL> file for how to build Perl.
123 The F<README> file for general stuff.
125 The F<Artistic> and F<Copying> files for copyright information.