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.23.0
12 This document describes differences between the 5.22.0 release and the 5.23.0
17 XXX Any important notices here
19 =head1 Core Enhancements
21 XXX New core language features go here. Summarize user-visible core language
22 enhancements. Particularly prominent performance optimisations could go
23 here, but most should go in the L</Performance Enhancements> section.
25 [ List each enhancement as a =head2 entry ]
29 XXX Any security-related notices go here. In particular, any security
30 vulnerabilities closed should be noted here rather than in the
31 L</Selected Bug Fixes> section.
33 [ List each security issue as a =head2 entry ]
35 =head1 Incompatible Changes
37 XXX For a release on a stable branch, this section aspires to be:
39 There are no changes intentionally incompatible with 5.XXX.XXX
40 If any exist, they are bugs, and we request that you submit a
41 report. See L</Reporting Bugs> below.
43 [ List each incompatible change as a =head2 entry ]
47 XXX Any deprecated features, syntax, modules etc. should be listed here.
49 =head2 Module removals
51 XXX Remove this section if inapplicable.
53 The following modules will be removed from the core distribution in a
54 future release, and will at that time need to be installed from CPAN.
55 Distributions on CPAN which require these modules will need to list them as
58 The core versions of these modules will now issue C<"deprecated">-category
59 warnings to alert you to this fact. To silence these deprecation warnings,
60 install the modules in question from CPAN.
62 Note that these are (with rare exceptions) fine modules that you are encouraged
63 to continue to use. Their disinclusion from core primarily hinges on their
64 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
65 not usually on concerns over their design.
71 XXX Note that deprecated modules should be listed here even if they are listed
72 as an updated module in the L</Modules and Pragmata> section.
76 [ List each other deprecation as a =head2 entry ]
78 =head1 Performance Enhancements
80 XXX Changes which enhance performance without changing behaviour go here.
81 There may well be none in a stable release.
83 [ List each enhancement as a =item entry ]
93 =head1 Modules and Pragmata
95 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
96 go here. If Module::CoreList is updated, generate an initial draft of the
97 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
98 for important changes should then be added by hand. In an ideal world,
99 dual-life modules would have a F<Changes> file that could be cribbed.
101 [ Within each section, list entries as a =item entry ]
103 =head2 New Modules and Pragmata
113 =head2 Updated Modules and Pragmata
119 L<Math::BigInt> has been upgraded from version 1.9997 to 1.999701.
121 Correct the behaviour of bdiv() and bmod() in list context. [perl #124300]
123 Correct C<< Math::BigInt->new() >> for non-integer input. [perl #124325]
125 Speed up Math::BigFloat -> blog(). [perl #124382]
127 Fix bug in Math::BigFloat's bceil() and bint() methods. [perl #124412]
131 L<Math::BigRat> has been upgraded from version 0.2608 to 0.260801.
133 Correct the behaviour of bdiv() and bmod() in list context. [perl #124303]
137 L<perl5db.pl> has been upgraded from version 1.49 to 1.49_01.
139 User actions are no longer evaluated after the script under the
140 debugger finishes. [perl #71678]
144 =head2 Removed Modules and Pragmata
156 XXX Changes to files in F<pod/> go here. Consider grouping entries by
157 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
159 =head2 New Documentation
161 XXX Changes which create B<new> files in F<pod/> go here.
165 XXX Description of the purpose of the new file here
167 =head2 Changes to Existing Documentation
169 XXX Changes which significantly change existing files in F<pod/> go here.
170 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
179 XXX Description of the change here
185 The following additions or changes have been made to diagnostic output,
186 including warnings and fatal error messages. For the complete list of
187 diagnostic messages, see L<perldiag>.
189 XXX New or changed warnings emitted by the core's C<C> code go here. Also
190 include any changes in L<perldiag> that reconcile it to the C<C> code.
192 =head2 New Diagnostics
194 XXX Newly added diagnostic messages go under here, separated into New Errors
203 XXX L<message|perldiag/"message">
213 XXX L<message|perldiag/"message">
217 =head2 Changes to Existing Diagnostics
219 XXX Changes (i.e. rewording) of diagnostic messages go here
225 XXX Describe change here
229 =head1 Utility Changes
231 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
232 Most of these are built within the directory F<utils>.
234 [ List utility changes as a =head2 entry for each utility and =item
235 entries for each change
236 Use L<XXX> with program names to get proper documentation linking. ]
248 =head1 Configuration and Compilation
250 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
251 go here. Any other changes to the Perl build process should be listed here.
252 However, any platform-specific changes should be listed in the
253 L</Platform Support> section, instead.
255 [ List changes as a =item entry ].
267 XXX Any significant changes to the testing of a freshly built perl should be
268 listed here. Changes which create B<new> files in F<t/> go here as do any
269 large changes to the testing harness (e.g. when parallel testing was added).
270 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
271 that they represent may be covered elsewhere.
273 [ List each test improvement as a =item entry ]
283 =head1 Platform Support
285 XXX Any changes to platform support should be listed in the sections below.
287 [ Within the sections, list each platform as a =item entry with specific
288 changes as paragraphs below it. ]
292 XXX List any platforms that this version of perl compiles on, that previous
293 versions did not. These will either be enabled by new files in the F<hints/>
294 directories, or new subdirectories and F<README> files at the top level of the
299 =item XXX-some-platform
305 =head2 Discontinued Platforms
307 XXX List any platforms that this version of perl no longer compiles on.
311 =item XXX-some-platform
317 =head2 Platform-Specific Notes
319 XXX List any changes for specific platforms. This could include configuration
320 and compilation changes or changes in portability/compatibility. However,
321 changes within modules for platforms should generally be listed in the
322 L</Modules and Pragmata> section.
332 Visual C++ 2013 builds will now execute on XP and higher. Previously they would
333 only execute on Vista and higher.
339 =head1 Internal Changes
341 XXX Changes which affect the interface available to C<XS> code go here. Other
342 significant internal changes for future core maintainers should be noted as
345 [ List each change as a =item entry ]
355 =head1 Selected Bug Fixes
357 XXX Important bug fixes in the core language are summarized here. Bug fixes in
358 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
360 [ List each fix as a =item entry ]
366 Duplicating a closed file handle for write no longer creates a
367 filename of the form F<GLOB(0xXXXXXXXX)>. [perl #125115]
371 =head1 Known Problems
373 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
374 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
375 platform specific bugs also go here.
377 [ List each fix as a =item entry ]
387 =head1 Errata From Previous Releases
393 XXX Add anything here that we forgot to add, or were mistaken about, in
394 the perldelta of a previous release.
400 XXX If any significant core contributor has died, we've added a short obituary
403 =head1 Acknowledgements
405 XXX Generate this with:
407 perl Porting/acknowledgements.pl v5.23.0..HEAD
409 =head1 Reporting Bugs
411 If you find what you think is a bug, you might check the articles recently
412 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
413 https://rt.perl.org/ . There may also be information at
414 http://www.perl.org/ , the Perl Home Page.
416 If you believe you have an unreported bug, please run the L<perlbug> program
417 included with your release. Be sure to trim your bug down to a tiny but
418 sufficient test case. Your bug report, along with the output of C<perl -V>,
419 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
421 If the bug you are reporting has security implications, which make it
422 inappropriate to send to a publicly archived mailing list, then please send it
423 to perl5-security-report@perl.org. This points to a closed subscription
424 unarchived mailing list, which includes all the core committers, who will be
425 able to help assess the impact of issues, figure out a resolution, and help
426 co-ordinate the release of patches to mitigate or fix the problem across all
427 platforms on which Perl is supported. Please only use this address for
428 security issues in the Perl core, not for modules independently distributed on
433 The F<Changes> file for an explanation of how to view exhaustive details on
436 The F<INSTALL> file for how to build Perl.
438 The F<README> file for general stuff.
440 The F<Artistic> and F<Copying> files for copyright information.