5 [ this is a template for a new perldelta file. Any text flagged as
6 XXX needs to be processed before release. ]
8 perldelta - what is new for perl v5.13.0
12 This document describes differences between the 5.13.0 release and
15 If you are upgrading from an earlier release such as 5.10.0, first read
16 L<perl5120delta>, which describes differences between 5.10.0 and
21 XXX Any important notices here
23 =head1 Incompatible Changes
25 XXX For a release on a stable branch, this section aspires to be:
27 There are no changes intentionally incompatible with 5.XXX.XXX. If any
28 exist, they are bugs and reports are welcome.
31 =head1 Core Enhancements
33 =head2 "safe signals" optimization
35 Signal dispatch has been moved from the runloop into control ops. This should
36 give a few percent speed increase, and eliminates almost all of the speed
37 penalty caused by the introduction of "safe signals" in 5.8.0. Signals should
38 still be dispatched within the same statement as they were previously - if
39 this is not the case, or it is possible to create uninterruptable loops, this
40 is a bug, and reports are encouraged of how to recreate such issues.
42 =head2 Assignment to C<$0> sets the legacy process name with C<prctl()> on Linux
44 On Linux the legacy process name will be set with L<prctl(2)>, in
45 addition to altering the POSIX name via C<argv[0]> as perl has done
46 since version 4.000. Now system utilities that read the legacy process
47 name such as ps, top and killall will recognize the name you set when
48 assigning to C<$0>. The string you supply will be cut off at 16 bytes,
49 this is a limitation imposed by Linux.
53 XXX List any platforms that this version of perl compiles on, that previous
54 versions did not. These will either be enabled by new files in the F<hints/>
55 directories, or new subdirectories and F<README> files at the top level of the
58 =head1 Modules and Pragmata
60 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
61 go here. If Module::CoreList is updated, generate an initial draft of the
62 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
63 entries to STDOUT. Results can be pasted in place of the '=head2' entries
64 below. A paragraph summary for important changes should then be added by hand.
65 In an ideal world, dual-life modules would have a F<Changes> file that could be
68 =head2 New Modules and Pragmata
70 =head2 Pragmata Changes
72 =head2 Updated Modules
74 =head2 Removed Modules and Pragmata
76 =head1 Utility Changes
78 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
79 here. Most of these are built within the directories F<utils> and F<x2p>.
89 =head1 New Documentation
91 XXX Changes which create B<new> files in F<pod/> go here.
101 =head1 Changes to Existing Documentation
103 XXX Changes which significantly change existing files in F<pod/> go here.
104 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
107 =head1 Performance Enhancements
109 XXX Changes which enhance performance without changing behaviour go here. There
110 may well be none in a stable release.
120 =head1 Installation and Configuration Improvements
122 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
125 =head2 Configuration improvements
129 =head2 Compilation improvements
133 =head2 Platform Specific Changes
137 =item XXX-some-platform
143 =head1 Selected Bug Fixes
145 XXX Important bug fixes in the core language are summarised here.
146 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
147 L</Modules and Pragmata>.
157 =head1 New or Changed Diagnostics
159 XXX New or changed warnings emitted by the core's C<C> code go here.
169 =head1 Changed Internals
171 XXX Changes which affect the interface available to C<XS> code go here.
183 XXX Changes which create B<new> files in F<t/> go here. Changes to
184 existing files in F<t/> aren't worth summarising, although the bugs that
185 they represent may be.
195 =head1 Known Problems
197 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
198 tests that had to be C<TODO>ed for the release would be noted here, unless
199 they were specific to a particular platform (see below).
201 This is a list of some significant unfixed bugs, which are regressions
202 from either 5.XXX.XXX or 5.XXX.XXX.
214 XXX Add any new known deprecations here.
216 The following items are now deprecated.
226 =head1 Platform Specific Notes
228 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
229 stars here. It's probably best to group changes under the same section layout
230 as the main perldelta
234 XXX If any significant core contributor has died, we've added a short obituary
237 =head1 Acknowledgements
239 XXX The list of people to thank goes here.
242 =head1 Reporting Bugs
244 If you find what you think is a bug, you might check the articles
245 recently posted to the comp.lang.perl.misc newsgroup and the perl
246 bug database at http://rt.perl.org/perlbug/ . There may also be
247 information at http://www.perl.org/ , the Perl Home Page.
249 If you believe you have an unreported bug, please run the B<perlbug>
250 program included with your release. Be sure to trim your bug down
251 to a tiny but sufficient test case. Your bug report, along with the
252 output of C<perl -V>, will be sent off to perlbug@perl.org to be
253 analysed by the Perl porting team.
255 If the bug you are reporting has security implications, which make it
256 inappropriate to send to a publicly archived mailing list, then please send
257 it to perl5-security-report@perl.org. This points to a closed subscription
258 unarchived mailing list, which includes all the core committers, who be able
259 to help assess the impact of issues, figure out a resolution, and help
260 co-ordinate the release of patches to mitigate or fix the problem across all
261 platforms on which Perl is supported. Please only use this address for
262 security issues in the Perl core, not for modules independently
267 The F<Changes> file for an explanation of how to view exhaustive details
270 The F<INSTALL> file for how to build Perl.
272 The F<README> file for general stuff.
274 The F<Artistic> and F<Copying> files for copyright information.