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.1
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, first read
16 L<perl5120delta>, which describes differences between 5.10 and
21 XXX Any important notices here
23 =head1 Incompatible Changes
27 The backslash-c construct was designed as a way of specifying
28 non-printable characters, but there were no restrictions (on ASCII
29 platforms) on what the character following the C<c> could be. Now, that
30 character must be one of the ASCII characters.
32 =head1 Core Enhancements
34 XXX New core language features go here. Summarise user-visible core language
35 enhancements. Particularly prominent performance optimisations could go
36 here, but most should go in the L</Performance Enhancements> section.
40 XXX List any platforms that this version of perl compiles on, that previous
41 versions did not. These will either be enabled by new files in the F<hints/>
42 directories, or new subdirectories and F<README> files at the top level of the
45 =head1 Modules and Pragmata
47 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
48 go here. If Module::CoreList is updated, generate an initial draft of the
49 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
50 entries to STDOUT. Results can be pasted in place of the '=head2' entries
51 below. A paragraph summary for important changes should then be added by hand.
52 In an ideal world, dual-life modules would have a F<Changes> file that could be
55 =head2 New Modules and Pragmata
57 =head2 Pragmata Changes
59 =head2 Updated Modules
61 =head2 Removed Modules and Pragmata
63 =head1 Utility Changes
65 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
66 here. Most of these are built within the directories F<utils> and F<x2p>.
76 =head1 New Documentation
78 XXX Changes which create B<new> files in F<pod/> go here.
88 =head1 Changes to Existing Documentation
90 XXX Changes which significantly change existing files in F<pod/> go here.
91 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
94 =head1 Performance Enhancements
96 XXX Changes which enhance performance without changing behaviour go here. There
97 may well be none in a stable release.
107 =head1 Installation and Configuration Improvements
109 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
112 =head2 Configuration improvements
116 =head2 Compilation improvements
120 =head2 Platform Specific Changes
124 =item XXX-some-platform
130 =head1 Selected Bug Fixes
132 XXX Important bug fixes in the core language are summarised here.
133 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
134 L</Modules and Pragmata>.
144 =head1 New or Changed Diagnostics
146 XXX New or changed warnings emitted by the core's C<C> code go here.
156 =head1 Changed Internals
158 XXX Changes which affect the interface available to C<XS> code go here.
170 XXX Changes which create B<new> files in F<t/> go here. Changes to
171 existing files in F<t/> aren't worth summarising, although the bugs that
172 they represent may be.
182 =head1 Known Problems
184 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
185 tests that had to be C<TODO>ed for the release would be noted here, unless
186 they were specific to a particular platform (see below).
188 This is a list of some significant unfixed bugs, which are regressions
189 from either 5.XXX.XXX or 5.XXX.XXX.
201 XXX Add any new known deprecations here.
203 The following items are now deprecated.
213 =head1 Platform Specific Notes
215 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
216 stars here. It's probably best to group changes under the same section layout
217 as the main perldelta
221 XXX If any significant core contributor has died, we've added a short obituary
224 =head1 Acknowledgements
226 XXX The list of people to thank goes here.
229 =head1 Reporting Bugs
231 If you find what you think is a bug, you might check the articles
232 recently posted to the comp.lang.perl.misc newsgroup and the perl
233 bug database at http://rt.perl.org/perlbug/ . There may also be
234 information at http://www.perl.org/ , the Perl Home Page.
236 If you believe you have an unreported bug, please run the B<perlbug>
237 program included with your release. Be sure to trim your bug down
238 to a tiny but sufficient test case. Your bug report, along with the
239 output of C<perl -V>, will be sent off to perlbug@perl.org to be
240 analysed by the Perl porting team.
242 If the bug you are reporting has security implications, which make it
243 inappropriate to send to a publicly archived mailing list, then please send
244 it to perl5-security-report@perl.org. This points to a closed subscription
245 unarchived mailing list, which includes all the core committers, who be able
246 to help assess the impact of issues, figure out a resolution, and help
247 co-ordinate the release of patches to mitigate or fix the problem across all
248 platforms on which Perl is supported. Please only use this address for
249 security issues in the Perl core, not for modules independently
254 The F<Changes> file for an explanation of how to view exhaustive details
257 The F<INSTALL> file for how to build Perl.
259 The F<README> file for general stuff.
261 The F<Artistic> and F<Copying> files for copyright information.