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.11
12 This document describes differences between the 5.13.10 release and
15 If you are upgrading from an earlier release such as 5.13.9, first read
16 L<perl5139delta>, which describes differences between 5.13.9 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 XXX For a release on a stable branch, this section aspires to be:
43 There are no changes intentionally incompatible with 5.XXX.XXX. If any
44 exist, they are bugs and reports are welcome.
46 [ List each incompatible change as a =head2 entry ]
50 XXX Any deprecated features, syntax, modules etc. should be listed here.
51 In particular, deprecated modules should be listed here even if they are
52 listed as an updated module in the L</Modules and Pragmata> section.
54 [ List each deprecation as a =head2 entry ]
56 =head1 Performance Enhancements
58 XXX Changes which enhance performance without changing behaviour go here. There
59 may well be none in a stable release.
61 [ List each enhancement as a =item entry ]
71 =head1 Modules and Pragmata
73 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
74 go here. If Module::CoreList is updated, generate an initial draft of the
75 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
76 entries to STDOUT. Results can be pasted in place of the '=head2' entries
77 below. A paragraph summary for important changes should then be added by hand.
78 In an ideal world, dual-life modules would have a F<Changes> file that could be
81 [ Within each section, list entries as a =item entry ]
83 =head2 New Modules and Pragmata
93 =head2 Updated Modules and Pragmata
99 C<CPANPLUS> has been upgraded from version 0.9101 to 0.9102
103 C<CPANPLUS::Dist::Build> has been upgraded from version 0.52 to 0.54
107 C<Devel::DProf> has been upgraded from version 20110225.01 to 20110228.00.
111 C<Digest::SHA> has been upgraded from version 5.50 to 5.60
113 New SHA-512/224 and SHA-512/256 transforms ref. NIST Draft FIPS 180-4 (February 2011)
117 C<ExtUtils::Command> has been upgraded from version 1.16 to 1.17.
121 C<IO> has been upgraded from version 1.25_03 to 1.25_04.
125 C<JSON::PP> has been upgraded from version 2.27103 to 2.27104
129 C<Locale::Codes> has been upgraded from version 3.15 to 3.16
133 C<Math::BigInt> has been upgraded from version 1.992 to 1.993
137 C<Math::BigInt::FastCalc> has been upgraded from version 0.24_02 to 0.28
141 C<Test::Harness> has been upgraded from version 3.22 to 3.23
145 C<Test::Simple> has been upgraded from version 0.97_01 to 0.98
149 C<Tie::RefHash> has been upgraded from version 1.38 to 1.39.
153 Unicode::UCD has been upgraded from version 0.31 to 0.32.
154 This includes a number of bug fixes:
164 It is now updated to Unicode Version 6 with Corrigendum #8, except,
165 as with Perl 5.14, the code point at U+1F514 has no name.
169 The Hangul syllable code points have the correct names, and their
170 decompositions are always output without requiring L<Lingua::KO::Hangul::Util>
175 The CJK (Chinese-Japanese-Korean) code points U+2A700 - U+2B734
176 and U+2B740 - 2B81D are now properly handled.
180 The numeric values are now output for those CJK code points that have them.
184 The names that are output for code points with multiple aliases are now the
191 This now correctly returns "Unknown" instead of C<undef> for the script
192 of a code point that hasn't been assigned another one.
196 This now correctly returns "No_Block" instead of C<undef> for the block
197 of a code point that hasn't been assigned to another one.
203 =head2 Removed Modules and Pragmata
215 XXX Changes to files in F<pod/> go here. Consider grouping entries by
216 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
218 =head2 New Documentation
220 XXX Changes which create B<new> files in F<pod/> go here.
224 XXX Description of the purpose of the new file here
226 =head2 Changes to Existing Documentation
228 XXX Changes which significantly change existing files in F<pod/> go here.
229 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
238 XXX Description of the change here
244 The following additions or changes have been made to diagnostic output,
245 including warnings and fatal error messages. For the complete list of
246 diagnostic messages, see L<perldiag>.
248 XXX New or changed warnings emitted by the core's C<C> code go here. Also
249 include any changes in L<perldiag> that reconcile it to the C<C> code.
251 [ Within each section, list entries as a =item entry ]
253 =head2 New Diagnostics
255 XXX Newly added diagnostic messages go here
265 =head2 Changes to Existing Diagnostics
267 XXX Changes (i.e. rewording) of diagnostic messages go here
277 =head1 Utility Changes
279 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
280 here. Most of these are built within the directories F<utils> and F<x2p>.
282 [ List utility changes as a =head3 entry for each utility and =item
283 entries for each change
284 Use L<XXX> with program names to get proper documentation linking. ]
296 =head1 Configuration and Compilation
298 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
299 go here. Any other changes to the Perl build process should be listed here.
300 However, any platform-specific changes should be listed in the
301 L</Platform Support> section, instead.
303 [ List changes as a =item entry ].
315 XXX Any significant changes to the testing of a freshly built perl should be
316 listed here. Changes which create B<new> files in F<t/> go here as do any
317 large changes to the testing harness (e.g. when parallel testing was added).
318 Changes to existing files in F<t/> aren't worth summarising, although the bugs
319 that they represent may be covered elsewhere.
321 [ List each test improvement as a =item entry ]
331 =head1 Platform Support
333 XXX Any changes to platform support should be listed in the sections below.
335 [ Within the sections, list each platform as a =item entry with specific
336 changes as paragraphs below it. ]
340 XXX List any platforms that this version of perl compiles on, that previous
341 versions did not. These will either be enabled by new files in the F<hints/>
342 directories, or new subdirectories and F<README> files at the top level of the
347 =item XXX-some-platform
353 =head2 Discontinued Platforms
355 XXX List any platforms that this version of perl no longer compiles on.
359 =item XXX-some-platform
365 =head2 Platform-Specific Notes
367 XXX List any changes for specific platforms. This could include configuration
368 and compilation changes or changes in portability/compatibility. However,
369 changes within modules for platforms should generally be listed in the
370 L</Modules and Pragmata> section.
374 =item XXX-some-platform
380 =head1 Internal Changes
382 XXX Changes which affect the interface available to C<XS> code go here.
383 Other significant internal changes for future core maintainers should
386 [ List each test improvement as a =item entry ]
396 =head1 Selected Bug Fixes
398 XXX Important bug fixes in the core language are summarised here.
399 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
400 L</Modules and Pragmata>.
402 [ List each fix as a =item entry ]
412 =head1 Known Problems
414 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
415 tests that had to be C<TODO>ed for the release would be noted here, unless
416 they were specific to a particular platform (see below).
418 This is a list of some significant unfixed bugs, which are regressions
419 from either 5.XXX.XXX or 5.XXX.XXX.
421 [ List each fix as a =item entry ]
433 XXX If any significant core contributor has died, we've added a short obituary
436 =head1 Acknowledgements
438 XXX The list of people to thank goes here.
440 =head1 Reporting Bugs
442 If you find what you think is a bug, you might check the articles
443 recently posted to the comp.lang.perl.misc newsgroup and the perl
444 bug database at http://rt.perl.org/perlbug/ . There may also be
445 information at http://www.perl.org/ , the Perl Home Page.
447 If you believe you have an unreported bug, please run the L<perlbug>
448 program included with your release. Be sure to trim your bug down
449 to a tiny but sufficient test case. Your bug report, along with the
450 output of C<perl -V>, will be sent off to perlbug@perl.org to be
451 analysed by the Perl porting team.
453 If the bug you are reporting has security implications, which make it
454 inappropriate to send to a publicly archived mailing list, then please send
455 it to perl5-security-report@perl.org. This points to a closed subscription
456 unarchived mailing list, which includes all the core committers, who be able
457 to help assess the impact of issues, figure out a resolution, and help
458 co-ordinate the release of patches to mitigate or fix the problem across all
459 platforms on which Perl is supported. Please only use this address for
460 security issues in the Perl core, not for modules independently
465 The F<Changes> file for an explanation of how to view exhaustive details
468 The F<INSTALL> file for how to build Perl.
470 The F<README> file for general stuff.
472 The F<Artistic> and F<Copying> files for copyright information.