3 [ this is a template for a new perldelta file. Any text flagged as
4 XXX needs to be processed before release. ]
6 perldelta - what is new for perl v5.11.5
10 This document describes differences between the 5.11.4 release and
13 If you are upgrading from an earlier release such as 5.11.3, first read
14 L<perl5114delta>, which describes differences between 5.11.3 and
19 XXX Any important notices here
21 =head1 Incompatible Changes
23 XXX For a release on a stable branch, this section aspires to be:
25 There are no changes intentionally incompatible with 5.XXX.XXX. If any
26 exist, they are bugs and reports are welcome.
29 =head1 Core Enhancements
31 XXX New core language features go here. Summarise user-visible core language
32 enhancements. Particularly prominent performance optimisations could go
33 here, but most should go in the L</Performance Enhancements> section.
37 XXX List any platforms that this version of perl compiles on, that previous
38 versions did not. These will either be enabled by new files in the F<hints/>
39 directories, or new subdirectories and F<README> files at the top level of the
42 =head1 Modules and Pragmata
44 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
45 go here. If Module::CoreList is updated, generate an initial draft of the
46 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
47 entries to STDOUT. Results can be pasted in place of the '=head2' entries
48 below. A paragraph summary for important changes should then be added by hand.
49 In an ideal world, dual-life modules would have a F<Changes> file that could be
52 =head2 New Modules and Pragmata
54 =head2 Pragmata Changes
56 =head2 Updated Modules
58 =head2 Removed Modules and Pragmata
60 =head1 Utility Changes
62 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
63 here. Most of these are built within the directories F<utils> and F<x2p>.
73 =head1 New Documentation
75 XXX Changes which create B<new> files in F<pod/> go here.
85 =head1 Changes to Existing Documentation
87 XXX Changes which significantly change existing files in F<pod/> go here.
88 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
91 =head1 Performance Enhancements
93 XXX Changes which enhance performance without changing behaviour go here. There
94 may well be none in a stable release.
104 =head1 Installation and Configuration Improvements
106 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
109 =head2 Configuration improvements
113 =head2 Compilation improvements
117 =head2 Platform Specific Changes
121 =item XXX-some-platform
127 =head1 Selected Bug Fixes
129 XXX Important bug fixes in the core language are summarised here.
130 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
131 L</Modules and Pragmata>.
141 =head1 New or Changed Diagnostics
143 XXX New or changed warnings emitted by the core's C<C> code go here.
153 =head1 Changed Internals
155 XXX Changes which affect the interface available to C<XS> code go here.
167 XXX Changes which create B<new> files in F<t/> go here. Changes to
168 existing files in F<t/> aren't worth summarising, although the bugs that
169 they represent may be.
179 =head1 Known Problems
181 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
182 tests that had to be C<TODO>ed for the release would be noted here, unless
183 they were specific to a particular platform (see below).
185 This is a list of some significant unfixed bugs, which are regressions
186 from either 5.XXX.XXX or 5.XXX.XXX.
198 XXX Add any new known deprecations here.
200 The following items are now deprecated.
210 =head1 Platform Specific Notes
212 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
213 stars here. It's probably best to group changes under the same section layout
214 as the main perldelta
218 XXX If any significant core contributor has died, we've added a short obituary
221 =head1 Acknowledgements
223 XXX The list of people to thank goes here.
226 =head1 Reporting Bugs
228 If you find what you think is a bug, you might check the articles
229 recently posted to the comp.lang.perl.misc newsgroup and the perl
230 bug database at http://rt.perl.org/perlbug/ . There may also be
231 information at http://www.perl.org/ , the Perl Home Page.
233 If you believe you have an unreported bug, please run the B<perlbug>
234 program included with your release. Be sure to trim your bug down
235 to a tiny but sufficient test case. Your bug report, along with the
236 output of C<perl -V>, will be sent off to perlbug@perl.org to be
237 analysed by the Perl porting team.
239 If the bug you are reporting has security implications, which make it
240 inappropriate to send to a publicly archived mailing list, then please send
241 it to perl5-security-report@perl.org. This points to a closed subscription
242 unarchived mailing list, which includes all the core committers, who be able
243 to help assess the impact of issues, figure out a resolution, and help
244 co-ordinate the release of patches to mitigate or fix the problem across all
245 platforms on which Perl is supported. Please only use this address for
246 security issues in the Perl core, not for modules independently
251 The F<Changes> file for an explanation of how to view exhaustive details
254 The F<INSTALL> file for how to build Perl.
256 The F<README> file for general stuff.
258 The F<Artistic> and F<Copying> files for copyright information.