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.15.0
12 This document describes differences between the 5.15.0 release and
15 If you are upgrading from an earlier release such as 5.YYY.YYY, first read
16 L<perl5YYYdelta>, which describes differences between 5.ZZZ.ZZZ and
21 XXX Any important notices here
23 =head1 Core Enhancements
25 XXX New core language features go here. Summarise user-visible core language
26 enhancements. Particularly prominent performance optimisations could go
27 here, but most should go in the L</Performance Enhancements> section.
29 [ List each enhancement as a =head2 entry ]
33 XXX Any security-related notices go here. In particular, any security
34 vulnerabilities closed should be noted here rather than in the
35 L</Selected Bug Fixes> section.
37 [ List each security issue as a =head2 entry ]
39 =head1 Incompatible Changes
41 [ List each incompatible change as a =head2 entry ]
45 XXX Any deprecated features, syntax, modules etc. should be listed here.
46 In particular, deprecated modules should be listed here even if they are
47 listed as an updated module in the L</Modules and Pragmata> section.
49 [ List each deprecation as a =head2 entry ]
51 =head1 Performance Enhancements
53 XXX Changes which enhance performance without changing behaviour go here. There
54 may well be none in a stable release.
56 [ List each enhancement as a =item entry ]
66 =head1 Modules and Pragmata
68 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
69 go here. If Module::CoreList is updated, generate an initial draft of the
70 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
71 entries to STDOUT. Results can be pasted in place of the '=head2' entries
72 below. A paragraph summary for important changes should then be added by hand.
73 In an ideal world, dual-life modules would have a F<Changes> file that could be
76 [ Within each section, list entries as a =item entry ]
78 =head2 New Modules and Pragmata
88 =head2 Updated Modules and Pragmata
94 C<Math::Complex> has been upgraded from version 1.56 to version 1.57.
96 Correct copy constructor usage.
97 Fix polarwise formatting with numeric format specifier.
98 More stable C<great_circle_direction> algorithm.
102 C<Time::HiRes> has been upgraded from version 1.9721_01 to version 1.9722.
104 Portability fix, and avoiding some compiler warnings.
112 =head2 Removed Modules and Pragmata
124 XXX Changes to files in F<pod/> go here. Consider grouping entries by
125 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
127 =head2 New Documentation
129 XXX Changes which create B<new> files in F<pod/> go here.
133 XXX Description of the purpose of the new file here
135 =head2 Changes to Existing Documentation
137 XXX Changes which significantly change existing files in F<pod/> go here.
138 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
147 XXX Description of the change here
153 The following additions or changes have been made to diagnostic output,
154 including warnings and fatal error messages. For the complete list of
155 diagnostic messages, see L<perldiag>.
157 XXX New or changed warnings emitted by the core's C<C> code go here. Also
158 include any changes in L<perldiag> that reconcile it to the C<C> code.
160 [ Within each section, list entries as a =item entry ]
162 =head2 New Diagnostics
164 XXX Newly added diagnostic messages go here
174 =head2 Changes to Existing Diagnostics
176 XXX Changes (i.e. rewording) of diagnostic messages go here
186 =head1 Utility Changes
188 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
189 here. Most of these are built within the directories F<utils> and F<x2p>.
191 [ List utility changes as a =head3 entry for each utility and =item
192 entries for each change
193 Use L<XXX> with program names to get proper documentation linking. ]
205 =head1 Configuration and Compilation
207 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
208 go here. Any other changes to the Perl build process should be listed here.
209 However, any platform-specific changes should be listed in the
210 L</Platform Support> section, instead.
212 [ List changes as a =item entry ].
224 XXX Any significant changes to the testing of a freshly built perl should be
225 listed here. Changes which create B<new> files in F<t/> go here as do any
226 large changes to the testing harness (e.g. when parallel testing was added).
227 Changes to existing files in F<t/> aren't worth summarising, although the bugs
228 that they represent may be covered elsewhere.
230 [ List each test improvement as a =item entry ]
240 =head1 Platform Support
242 XXX Any changes to platform support should be listed in the sections below.
244 [ Within the sections, list each platform as a =item entry with specific
245 changes as paragraphs below it. ]
249 XXX List any platforms that this version of perl compiles on, that previous
250 versions did not. These will either be enabled by new files in the F<hints/>
251 directories, or new subdirectories and F<README> files at the top level of the
256 =item XXX-some-platform
262 =head2 Discontinued Platforms
264 XXX List any platforms that this version of perl no longer compiles on.
268 =item XXX-some-platform
274 =head2 Platform-Specific Notes
276 XXX List any changes for specific platforms. This could include configuration
277 and compilation changes or changes in portability/compatibility. However,
278 changes within modules for platforms should generally be listed in the
279 L</Modules and Pragmata> section.
283 =item XXX-some-platform
289 =head1 Internal Changes
291 XXX Changes which affect the interface available to C<XS> code go here.
292 Other significant internal changes for future core maintainers should
299 The compiled representation of formats is now stored via the mg_ptr of
300 their PERL_MAGIC_fm. Previously it was stored in the string buffer,
301 beyond SvLEN(), the regular end of the string. SvCOMPILED() and
302 SvCOMPILED_{on,off}() now exist solely for compatibility for XS code.
303 The first is always 0, the other two now no-ops.
307 =head1 Selected Bug Fixes
309 XXX Important bug fixes in the core language are summarised here.
310 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
311 L</Modules and Pragmata>.
313 [ List each fix as a =item entry ]
323 =head1 Known Problems
325 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
326 tests that had to be C<TODO>ed for the release would be noted here, unless
327 they were specific to a particular platform (see below).
329 This is a list of some significant unfixed bugs, which are regressions
330 from either 5.XXX.XXX or 5.XXX.XXX.
332 [ List each fix as a =item entry ]
344 XXX If any significant core contributor has died, we've added a short obituary
347 =head1 Acknowledgements
349 XXX The list of people to thank goes here.
351 =head1 Reporting Bugs
353 If you find what you think is a bug, you might check the articles
354 recently posted to the comp.lang.perl.misc newsgroup and the perl
355 bug database at http://rt.perl.org/perlbug/ . There may also be
356 information at http://www.perl.org/ , the Perl Home Page.
358 If you believe you have an unreported bug, please run the L<perlbug>
359 program included with your release. Be sure to trim your bug down
360 to a tiny but sufficient test case. Your bug report, along with the
361 output of C<perl -V>, will be sent off to perlbug@perl.org to be
362 analysed by the Perl porting team.
364 If the bug you are reporting has security implications, which make it
365 inappropriate to send to a publicly archived mailing list, then please send
366 it to perl5-security-report@perl.org. This points to a closed subscription
367 unarchived mailing list, which includes all the core committers, who be able
368 to help assess the impact of issues, figure out a resolution, and help
369 co-ordinate the release of patches to mitigate or fix the problem across all
370 platforms on which Perl is supported. Please only use this address for
371 security issues in the Perl core, not for modules independently
376 The F<Changes> file for an explanation of how to view exhaustive details
379 The F<INSTALL> file for how to build Perl.
381 The F<README> file for general stuff.
383 The F<Artistic> and F<Copying> files for copyright information.