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.
44 XXX List any platforms that this version of perl compiles on, that previous
45 versions did not. These will either be enabled by new files in the F<hints/>
46 directories, or new subdirectories and F<README> files at the top level of the
49 =head1 Modules and Pragmata
51 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
52 go here. If Module::CoreList is updated, generate an initial draft of the
53 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
54 entries to STDOUT. Results can be pasted in place of the '=head2' entries
55 below. A paragraph summary for important changes should then be added by hand.
56 In an ideal world, dual-life modules would have a F<Changes> file that could be
59 =head2 New Modules and Pragmata
61 =head2 Pragmata Changes
63 =head2 Updated Modules
65 =head2 Removed Modules and Pragmata
67 =head1 Utility Changes
69 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
70 here. Most of these are built within the directories F<utils> and F<x2p>.
80 =head1 New Documentation
82 XXX Changes which create B<new> files in F<pod/> go here.
92 =head1 Changes to Existing Documentation
94 XXX Changes which significantly change existing files in F<pod/> go here.
95 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
98 =head1 Performance Enhancements
100 XXX Changes which enhance performance without changing behaviour go here. There
101 may well be none in a stable release.
111 =head1 Installation and Configuration Improvements
113 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
116 =head2 Configuration improvements
120 =head2 Compilation improvements
124 =head2 Platform Specific Changes
128 =item XXX-some-platform
134 =head1 Selected Bug Fixes
136 XXX Important bug fixes in the core language are summarised here.
137 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
138 L</Modules and Pragmata>.
148 =head1 New or Changed Diagnostics
150 XXX New or changed warnings emitted by the core's C<C> code go here.
160 =head1 Changed Internals
162 XXX Changes which affect the interface available to C<XS> code go here.
174 XXX Changes which create B<new> files in F<t/> go here. Changes to
175 existing files in F<t/> aren't worth summarising, although the bugs that
176 they represent may be.
186 =head1 Known Problems
188 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
189 tests that had to be C<TODO>ed for the release would be noted here, unless
190 they were specific to a particular platform (see below).
192 This is a list of some significant unfixed bugs, which are regressions
193 from either 5.XXX.XXX or 5.XXX.XXX.
205 XXX Add any new known deprecations here.
207 The following items are now deprecated.
217 =head1 Platform Specific Notes
219 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
220 stars here. It's probably best to group changes under the same section layout
221 as the main perldelta
225 XXX If any significant core contributor has died, we've added a short obituary
228 =head1 Acknowledgements
230 XXX The list of people to thank goes here.
233 =head1 Reporting Bugs
235 If you find what you think is a bug, you might check the articles
236 recently posted to the comp.lang.perl.misc newsgroup and the perl
237 bug database at http://rt.perl.org/perlbug/ . There may also be
238 information at http://www.perl.org/ , the Perl Home Page.
240 If you believe you have an unreported bug, please run the B<perlbug>
241 program included with your release. Be sure to trim your bug down
242 to a tiny but sufficient test case. Your bug report, along with the
243 output of C<perl -V>, will be sent off to perlbug@perl.org to be
244 analysed by the Perl porting team.
246 If the bug you are reporting has security implications, which make it
247 inappropriate to send to a publicly archived mailing list, then please send
248 it to perl5-security-report@perl.org. This points to a closed subscription
249 unarchived mailing list, which includes all the core committers, who be able
250 to help assess the impact of issues, figure out a resolution, and help
251 co-ordinate the release of patches to mitigate or fix the problem across all
252 platforms on which Perl is supported. Please only use this address for
253 security issues in the Perl core, not for modules independently
258 The F<Changes> file for an explanation of how to view exhaustive details
261 The F<INSTALL> file for how to build Perl.
263 The F<README> file for general stuff.
265 The F<Artistic> and F<Copying> files for copyright information.