5 [ this is a template for a new perldelta file. Any text flagged as XXX needs
6 to be processed before release. ]
8 perldelta - what is new for perl v5.21.11
12 This document describes differences between the 5.21.10 release and the 5.21.11
15 If you are upgrading from an earlier release such as 5.21.9, first read
16 L<perl52110delta>, which describes differences between 5.21.9 and 5.21.10.
20 XXX Any important notices here
22 =head1 Core Enhancements
24 XXX New core language features go here. Summarize user-visible core language
25 enhancements. Particularly prominent performance optimisations could go
26 here, but most should go in the L</Performance Enhancements> section.
28 [ List each enhancement as a =head2 entry ]
32 XXX Any security-related notices go here. In particular, any security
33 vulnerabilities closed should be noted here rather than in the
34 L</Selected Bug Fixes> section.
36 [ List each security issue as a =head2 entry ]
38 =head1 Incompatible Changes
40 XXX For a release on a stable branch, this section aspires to be:
42 There are no changes intentionally incompatible with 5.XXX.XXX
43 If any exist, they are bugs, and we request that you submit a
44 report. See L</Reporting Bugs> below.
46 [ List each incompatible change as a =head2 entry ]
50 XXX Any deprecated features, syntax, modules etc. should be listed here.
52 =head2 Making all warnings fatal is discouraged
54 The documentation for L<fatal warnings|warnings/Fatal Warnings> notes
55 that C<< use warnings FATAL => 'all' >> is discouraged
56 and provides stronger language about the risks of fatal warnings
59 =head2 Module removals
61 XXX Remove this section if inapplicable.
63 The following modules will be removed from the core distribution in a
64 future release, and will at that time need to be installed from CPAN.
65 Distributions on CPAN which require these modules will need to list them as
68 The core versions of these modules will now issue C<"deprecated">-category
69 warnings to alert you to this fact. To silence these deprecation warnings,
70 install the modules in question from CPAN.
72 Note that these are (with rare exceptions) fine modules that you are encouraged
73 to continue to use. Their disinclusion from core primarily hinges on their
74 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
75 not usually on concerns over their design.
81 XXX Note that deprecated modules should be listed here even if they are listed
82 as an updated module in the L</Modules and Pragmata> section.
86 [ List each other deprecation as a =head2 entry ]
88 =head1 Performance Enhancements
90 XXX Changes which enhance performance without changing behaviour go here.
91 There may well be none in a stable release.
93 [ List each enhancement as a =item entry ]
103 =head1 Modules and Pragmata
105 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
106 go here. If Module::CoreList is updated, generate an initial draft of the
107 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
108 for important changes should then be added by hand. In an ideal world,
109 dual-life modules would have a F<Changes> file that could be cribbed.
111 [ Within each section, list entries as a =item entry ]
113 =head2 New Modules and Pragmata
123 =head2 Updated Modules and Pragmata
129 L<attributes> has been upgraded from version 0.26 to 0.27.
133 L<Cwd> has been upgraded from version 3.55 to 3.56.
137 L<ExtUtils::Miniperl> has been upgraded from version 1.04 to 1.05.
141 FindExt has been upgraded from version 1.02 to 1.03.
145 L<IO::Socket::IP> has been upgraded from version 0.36 to 0.37.
149 L<Module::CoreList> has been upgraded from version 5.20150320 to 5.20150420.
151 Updated to cover the latest releases of Perl.
155 L<PerlIO::mmap> has been upgraded from version 0.013 to 0.014.
159 L<utf8> has been upgraded from version 1.15 to 1.16.
163 L<warnings> has been upgraded from version 1.31 to 1.32.
167 =head2 Removed Modules and Pragmata
179 XXX Changes to files in F<pod/> go here. Consider grouping entries by
180 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
182 =head2 New Documentation
184 XXX Changes which create B<new> files in F<pod/> go here.
188 XXX Description of the purpose of the new file here
190 =head2 Changes to Existing Documentation
192 XXX Changes which significantly change existing files in F<pod/> go here.
193 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
202 XXX Description of the change here
208 The following additions or changes have been made to diagnostic output,
209 including warnings and fatal error messages. For the complete list of
210 diagnostic messages, see L<perldiag>.
212 XXX New or changed warnings emitted by the core's C<C> code go here. Also
213 include any changes in L<perldiag> that reconcile it to the C<C> code.
215 =head2 New Diagnostics
217 XXX Newly added diagnostic messages go under here, separated into New Errors
226 XXX L<message|perldiag/"message">
236 XXX L<message|perldiag/"message">
240 =head2 Changes to Existing Diagnostics
242 XXX Changes (i.e. rewording) of diagnostic messages go here
248 XXX Describe change here
252 =head1 Utility Changes
254 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
255 Most of these are built within the directory F<utils>.
257 [ List utility changes as a =head2 entry for each utility and =item
258 entries for each change
259 Use L<XXX> with program names to get proper documentation linking. ]
271 =head1 Configuration and Compilation
273 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
274 go here. Any other changes to the Perl build process should be listed here.
275 However, any platform-specific changes should be listed in the
276 L</Platform Support> section, instead.
278 [ List changes as a =item entry ].
290 XXX Any significant changes to the testing of a freshly built perl should be
291 listed here. Changes which create B<new> files in F<t/> go here as do any
292 large changes to the testing harness (e.g. when parallel testing was added).
293 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
294 that they represent may be covered elsewhere.
296 [ List each test improvement as a =item entry ]
306 =head1 Platform Support
308 XXX Any changes to platform support should be listed in the sections below.
310 [ Within the sections, list each platform as a =item entry with specific
311 changes as paragraphs below it. ]
315 XXX List any platforms that this version of perl compiles on, that previous
316 versions did not. These will either be enabled by new files in the F<hints/>
317 directories, or new subdirectories and F<README> files at the top level of the
322 =item XXX-some-platform
328 =head2 Discontinued Platforms
330 XXX List any platforms that this version of perl no longer compiles on.
334 =item XXX-some-platform
340 =head2 Platform-Specific Notes
342 XXX List any changes for specific platforms. This could include configuration
343 and compilation changes or changes in portability/compatibility. However,
344 changes within modules for platforms should generally be listed in the
345 L</Modules and Pragmata> section.
349 =item XXX-some-platform
355 =head1 Internal Changes
357 XXX Changes which affect the interface available to C<XS> code go here. Other
358 significant internal changes for future core maintainers should be noted as
361 [ List each change as a =item entry ]
371 =head1 Selected Bug Fixes
373 XXX Important bug fixes in the core language are summarized here. Bug fixes in
374 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
376 [ List each fix as a =item entry ]
386 =head1 Known Problems
388 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
389 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
390 platform specific bugs also go here.
392 [ List each fix as a =item entry ]
402 =head1 Errata From Previous Releases
408 XXX Add anything here that we forgot to add, or were mistaken about, in
409 the perldelta of a previous release.
415 XXX If any significant core contributor has died, we've added a short obituary
418 =head1 Acknowledgements
420 XXX Generate this with:
422 perl Porting/acknowledgements.pl v5.21.10..HEAD
424 =head1 Reporting Bugs
426 If you find what you think is a bug, you might check the articles recently
427 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
428 https://rt.perl.org/ . There may also be information at
429 http://www.perl.org/ , the Perl Home Page.
431 If you believe you have an unreported bug, please run the L<perlbug> program
432 included with your release. Be sure to trim your bug down to a tiny but
433 sufficient test case. Your bug report, along with the output of C<perl -V>,
434 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
436 If the bug you are reporting has security implications, which make it
437 inappropriate to send to a publicly archived mailing list, then please send it
438 to perl5-security-report@perl.org. This points to a closed subscription
439 unarchived mailing list, which includes all the core committers, who will be
440 able to help assess the impact of issues, figure out a resolution, and help
441 co-ordinate the release of patches to mitigate or fix the problem across all
442 platforms on which Perl is supported. Please only use this address for
443 security issues in the Perl core, not for modules independently distributed on
448 The F<Changes> file for an explanation of how to view exhaustive details on
451 The F<INSTALL> file for how to build Perl.
453 The F<README> file for general stuff.
455 The F<Artistic> and F<Copying> files for copyright information.