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 XXX New core language features go here. Summarise user-visible core language
34 enhancements. Particularly prominent performance optimisations could go
35 here, but most should go in the L</Performance Enhancements> section.
39 XXX List any platforms that this version of perl compiles on, that previous
40 versions did not. These will either be enabled by new files in the F<hints/>
41 directories, or new subdirectories and F<README> files at the top level of the
44 =head1 Modules and Pragmata
46 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
47 go here. If Module::CoreList is updated, generate an initial draft of the
48 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
49 entries to STDOUT. Results can be pasted in place of the '=head2' entries
50 below. A paragraph summary for important changes should then be added by hand.
51 In an ideal world, dual-life modules would have a F<Changes> file that could be
54 =head2 New Modules and Pragmata
56 =head2 Pragmata Changes
58 =head2 Updated Modules
60 =head2 Removed Modules and Pragmata
62 =head1 Utility Changes
64 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
65 here. Most of these are built within the directories F<utils> and F<x2p>.
75 =head1 New Documentation
77 XXX Changes which create B<new> files in F<pod/> go here.
87 =head1 Changes to Existing Documentation
89 XXX Changes which significantly change existing files in F<pod/> go here.
90 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
93 =head1 Performance Enhancements
95 XXX Changes which enhance performance without changing behaviour go here. There
96 may well be none in a stable release.
106 =head1 Installation and Configuration Improvements
108 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
111 =head2 Configuration improvements
115 =head2 Compilation improvements
119 =head2 Platform Specific Changes
123 =item XXX-some-platform
129 =head1 Selected Bug Fixes
131 XXX Important bug fixes in the core language are summarised here.
132 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
133 L</Modules and Pragmata>.
143 =head1 New or Changed Diagnostics
145 XXX New or changed warnings emitted by the core's C<C> code go here.
155 =head1 Changed Internals
157 XXX Changes which affect the interface available to C<XS> code go here.
169 XXX Changes which create B<new> files in F<t/> go here. Changes to
170 existing files in F<t/> aren't worth summarising, although the bugs that
171 they represent may be.
181 =head1 Known Problems
183 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
184 tests that had to be C<TODO>ed for the release would be noted here, unless
185 they were specific to a particular platform (see below).
187 This is a list of some significant unfixed bugs, which are regressions
188 from either 5.XXX.XXX or 5.XXX.XXX.
200 XXX Add any new known deprecations here.
202 The following items are now deprecated.
212 =head1 Platform Specific Notes
214 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
215 stars here. It's probably best to group changes under the same section layout
216 as the main perldelta
220 XXX If any significant core contributor has died, we've added a short obituary
223 =head1 Acknowledgements
225 XXX The list of people to thank goes here.
228 =head1 Reporting Bugs
230 If you find what you think is a bug, you might check the articles
231 recently posted to the comp.lang.perl.misc newsgroup and the perl
232 bug database at http://rt.perl.org/perlbug/ . There may also be
233 information at http://www.perl.org/ , the Perl Home Page.
235 If you believe you have an unreported bug, please run the B<perlbug>
236 program included with your release. Be sure to trim your bug down
237 to a tiny but sufficient test case. Your bug report, along with the
238 output of C<perl -V>, will be sent off to perlbug@perl.org to be
239 analysed by the Perl porting team.
241 If the bug you are reporting has security implications, which make it
242 inappropriate to send to a publicly archived mailing list, then please send
243 it to perl5-security-report@perl.org. This points to a closed subscription
244 unarchived mailing list, which includes all the core committers, who be able
245 to help assess the impact of issues, figure out a resolution, and help
246 co-ordinate the release of patches to mitigate or fix the problem across all
247 platforms on which Perl is supported. Please only use this address for
248 security issues in the Perl core, not for modules independently
253 The F<Changes> file for an explanation of how to view exhaustive details
256 The F<INSTALL> file for how to build Perl.
258 The F<README> file for general stuff.
260 The F<Artistic> and F<Copying> files for copyright information.