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.4
12 This document describes differences between the 5.21.3 release and the 5.21.4
15 If you are upgrading from an earlier release such as 5.21.2, first read
16 L<perl5213delta>, which describes differences between 5.21.2 and 5.21.3.
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 ]
30 =head2 Infinity and NaN (not-a-number) handling improved
32 Floating point values are able to hold the special values infinity
33 (also -infinity), and NaN (not-a-number). Now we more robustly recognize
34 and propagate the value in computations, and on output normalize them
37 See also the L<POSIX> enhancements.
41 XXX Any security-related notices go here. In particular, any security
42 vulnerabilities closed should be noted here rather than in the
43 L</Selected Bug Fixes> section.
45 [ List each security issue as a =head2 entry ]
47 =head1 Incompatible Changes
49 XXX For a release on a stable branch, this section aspires to be:
51 There are no changes intentionally incompatible with 5.XXX.XXX
52 If any exist, they are bugs, and we request that you submit a
53 report. See L</Reporting Bugs> below.
55 [ List each incompatible change as a =head2 entry ]
57 =head2 Changes to the C<*> prototype
59 The C<*> character in a subroutine's prototype used to allow barewords
60 to take precedence over most, but not all subroutines. It was never
61 consistent and exhibited buggy behaviour.
63 Now it has been changed, so subroutines always take precedence over
64 barewords, which brings it into conformity with similarly prototyped
69 splat(foo); # now always splat(foo())
70 splat(bar); # still splat('bar') as before
71 close(foo); # close(foo())
72 close(bar); # close('bar')
76 XXX Any deprecated features, syntax, modules etc. should be listed here.
78 =head2 Module removals
80 XXX Remove this section if inapplicable.
82 The following modules will be removed from the core distribution in a
83 future release, and will at that time need to be installed from CPAN.
84 Distributions on CPAN which require these modules will need to list them as
87 The core versions of these modules will now issue C<"deprecated">-category
88 warnings to alert you to this fact. To silence these deprecation warnings,
89 install the modules in question from CPAN.
91 Note that these are (with rare exceptions) fine modules that you are encouraged
92 to continue to use. Their disinclusion from core primarily hinges on their
93 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
94 not usually on concerns over their design.
100 XXX Note that deprecated modules should be listed here even if they are listed
101 as an updated module in the L</Modules and Pragmata> section.
105 [ List each other deprecation as a =head2 entry ]
107 =head1 Performance Enhancements
109 XXX Changes which enhance performance without changing behaviour go here.
110 There may well be none in a stable release.
112 [ List each enhancement as a =item entry ]
118 Subroutines with an empty prototype and bodies containing just C<undef> are
119 now eligible for inlining. [perl #122728]
123 =head1 Modules and Pragmata
125 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
126 go here. If Module::CoreList is updated, generate an initial draft of the
127 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
128 for important changes should then be added by hand. In an ideal world,
129 dual-life modules would have a F<Changes> file that could be cribbed.
131 [ Within each section, list entries as a =item entry ]
133 =head2 New Modules and Pragmata
143 =head2 Updated Modules and Pragmata
149 L<XXX> has been upgraded from version A.xx to B.yy.
153 L<B::Concise> has been upgraded from version 0.992 to 0.993.
157 L<CPAN::Meta::Requirements> has been upgraded from version 2.126 to 2.128.
161 L<ExtUtils::CBuilder> has been upgraded from version 0.280216 to 0.280219.
166 L<ExtUtils::Manifest> has been upgraded from version 1.65 to 1.66.
171 L<ExtUtils::ParseXS>: Documentation has been added to
172 F<ExtUtils-ParseXS/lib/perlxs.pod> concerning handling of locales when writing
177 L<File::Find> has been upgraded from version 1.27 to 1.28.
179 C<find()> and C<finddepth()> will now warn if passed inappropriate or
184 L<Getopt::Std> has been upgraded from version 1.10 to 1.11.
188 L<HTTP::Tiny> has been upgraded from version 0.047 to 0.048.
192 L<Module::CoreList> has been upgraded from version 5.021003 to 5.021004.
196 L<POSIX> has been upgraded from version 1.42 to 1.43.
198 The C99 math functions and constants (for example acosh, round,
199 M_E, M_PI) have been added.
203 L<Pod::Perldoc> has been upgraded from version 3.23 to 3.24.
207 Scalar-List-Utils has been upgraded from version 1.40 to 1.41.
211 L<constant> has been upgraded from version 1.31 to 1.32.
213 It now accepts fully-qualified constant names, allowing constants to be
214 defined in packages other than the caller.
218 L<threads> has been upgraded from version 1.95 to 1.96.
222 =head2 Removed Modules and Pragmata
234 XXX Changes to files in F<pod/> go here. Consider grouping entries by
235 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
237 =head2 New Documentation
239 XXX Changes which create B<new> files in F<pod/> go here.
243 XXX Description of the purpose of the new file here
245 =head2 Changes to Existing Documentation
247 XXX Changes which significantly change existing files in F<pod/> go here.
248 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
257 XXX Description of the change here
261 L<perlsyn>: An ambiguity in the documentation of the Ellipsis statement has
262 been corrected. [perl #122661]
268 The following additions or changes have been made to diagnostic output,
269 including warnings and fatal error messages. For the complete list of
270 diagnostic messages, see L<perldiag>.
272 XXX New or changed warnings emitted by the core's C<C> code go here. Also
273 include any changes in L<perldiag> that reconcile it to the C<C> code.
275 =head2 New Diagnostics
277 XXX Newly added diagnostic messages go under here, separated into New Errors
286 XXX L<message|perldiag/"message">
296 XXX L<message|perldiag/"message">
300 =head2 Changes to Existing Diagnostics
302 XXX Changes (i.e. rewording) of diagnostic messages go here
308 XXX Describe change here
312 =head2 Diagnostic Removals
318 "Constant is not a FOO reference"
320 Compile-time checking of constant dereferencing (e.g.,
321 C<< my_constant->() >>) has been removed, since it was not taking
322 overloading into account. [perl #69456] [perl #122607]
326 The warning "Ambiguous use of -foo resolved as -&foo()" has been removed.
327 There is actually no ambiguity here, and this impedes the use of negated
328 constants; e.g., C<-Inf>.
332 The little-known C<my Class $var> syntax (see L<fields> and L<attributes>)
333 could get confused in the scope of C<use utf8> if C<Class> were a constant
334 whose value contained Latin-1 characters.
338 =head1 Utility Changes
340 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
341 Most of these are built within the directory F<utils>.
343 [ List utility changes as a =head2 entry for each utility and =item
344 entries for each change
345 Use L<XXX> with program names to get proper documentation linking. ]
357 =head1 Configuration and Compilation
359 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
360 go here. Any other changes to the Perl build process should be listed here.
361 However, any platform-specific changes should be listed in the
362 L</Platform Support> section, instead.
364 [ List changes as a =item entry ].
376 XXX Any significant changes to the testing of a freshly built perl should be
377 listed here. Changes which create B<new> files in F<t/> go here as do any
378 large changes to the testing harness (e.g. when parallel testing was added).
379 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
380 that they represent may be covered elsewhere.
382 [ List each test improvement as a =item entry ]
392 =head1 Platform Support
394 XXX Any changes to platform support should be listed in the sections below.
396 [ Within the sections, list each platform as a =item entry with specific
397 changes as paragraphs below it. ]
401 XXX List any platforms that this version of perl compiles on, that previous
402 versions did not. These will either be enabled by new files in the F<hints/>
403 directories, or new subdirectories and F<README> files at the top level of the
408 =item XXX-some-platform
414 =head2 Discontinued Platforms
416 XXX List any platforms that this version of perl no longer compiles on.
420 =item XXX-some-platform
426 =head2 Platform-Specific Notes
428 XXX List any changes for specific platforms. This could include configuration
429 and compilation changes or changes in portability/compatibility. However,
430 changes within modules for platforms should generally be listed in the
431 L</Modules and Pragmata> section.
435 =item XXX-some-platform
441 =head1 Internal Changes
443 XXX Changes which affect the interface available to C<XS> code go here. Other
444 significant internal changes for future core maintainers should be noted as
447 [ List each change as a =item entry ]
455 =head1 Selected Bug Fixes
457 XXX Important bug fixes in the core language are summarized here. Bug fixes in
458 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
460 [ List each fix as a =item entry ]
470 Constant dereferencing now works correctly for typeglob constants.
471 Previously the glob was stringified and its name looked up. Now the glob
472 itself is used. [perl #69456]
476 When parsing a funny character ($ @ % &) followed by braces, the parser no
477 longer tries to guess whether it is a block or a hash constructor (causing
478 a syntax error when it guesses the latter), since it can only be a block.
482 C<undef $reference> now frees the referent immediately, instead of hanging
483 on to it until the next statement. [perl #122556]
487 Various cases where the name of a sub is used (autoload, overloading, error
488 messages) used to crash for lexical subs, but have been fixed.
492 Bareword lookup now tries to avoid vivifying packages if it turns out the
493 bareword is not going to be a subroutine name.
497 Compilation of anonymous constants (e.g., C<sub () { 3 }>) no longer
498 deletes any subroutine named C<__ANON__> in the current package. Not only
499 was C<*__ANON__{CODE}> cleared, but there was a memory leak, too. This bug
500 goes back to perl 5.8.0.
504 Stub declarations like C<sub f;> and C<sub f ();> no longer wipe out
505 constants of the same name declared by C<use constant>. This bug was
506 introduced in perl 5.10.0.
510 Under some conditions a warning raised in compilation of regular
511 expression patterns could be displayed multiple times. This is now
516 C<qr/[\N{named sequence}]/> now works properly in many instances. Some
517 names known to C<\N{...}> refer to a sequence of multiple characters,
518 instead of the usual single character. Bracketed character classes
519 generally only match single characters, but now special handling has
520 been added so that they can match named sequences, but not if the class
521 is inverted or the sequence is specified as the beginning or end of a
522 range. In these cases, the only behavior change from before is a slight
523 rewording of the fatal error message given when this class is part of a
524 C<?[...])> construct. When the C<[...]> stands alone, the same
525 non-fatal warning as before is raised, and only the first character in
526 the sequence is used, again just as before.
530 Tainted constants evaluated at compile time no longer cause unrelated
531 statements to become tainted. [perl #122669]
535 C<open $$fh, ...>, which vivifies a handle with a name like "main::_GEN_0",
536 was not giving the handle the right reference count, so a double free could
541 When deciding that a bareword was a method name, the parser would get
542 confused if an "our" sub with the same name existed, and look up the method
543 in the package of the "our" sub, instead of the package of the invocant.
547 The parser no longer gets confused by C<\U=> within a double-quoted string.
548 It used to roduce a syntax error, but now compiles it correctly.
553 It has always been the intention for the C<-B> and C<-T> file test
554 operators to treat UTF-8 encoded files as text.
555 (L<perlfunc|perlfunc/-X FILEHANDLE> has been updated to say this.)
556 Previously, it was possible for some files to be considered UTF-8 that
557 actually weren't valid UTF-8. This is now fixed. The operators now
558 work on EBCDIC platforms as well.
562 Under some conditions warning messages raised during regular expression
563 pattern compilation were being output more than once. This has now been
568 A regression has been fixed that was introduced in v5.20.0 (fixed in
569 v5.20.1 as well as here) in which a UTF-8 encoded regular expression
570 pattern that contains a single ASCII lowercase letter does not match its
571 uppercase counterpart. [perl #122655]
575 Constant folding could incorrectly suppress warnings if lexical warnings
576 (C<use warnings> or C<no warnings>) were not in effect and C<$^W> were
577 false at compile time and true at run time.
581 =head1 Known Problems
583 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
584 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
585 platform specific bugs also go here.
587 [ List each fix as a =item entry ]
597 =head1 Errata From Previous Releases
603 XXX Add anything here that we forgot to add, or were mistaken about, in
604 the perldelta of a previous release.
610 XXX If any significant core contributor has died, we've added a short obituary
613 =head1 Acknowledgements
615 XXX Generate this with:
617 perl Porting/acknowledgements.pl v5.21.3..HEAD
619 =head1 Reporting Bugs
621 If you find what you think is a bug, you might check the articles recently
622 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
623 https://rt.perl.org/ . There may also be information at
624 http://www.perl.org/ , the Perl Home Page.
626 If you believe you have an unreported bug, please run the L<perlbug> program
627 included with your release. Be sure to trim your bug down to a tiny but
628 sufficient test case. Your bug report, along with the output of C<perl -V>,
629 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
631 If the bug you are reporting has security implications, which make it
632 inappropriate to send to a publicly archived mailing list, then please send it
633 to perl5-security-report@perl.org. This points to a closed subscription
634 unarchived mailing list, which includes all the core committers, who will be
635 able to help assess the impact of issues, figure out a resolution, and help
636 co-ordinate the release of patches to mitigate or fix the problem across all
637 platforms on which Perl is supported. Please only use this address for
638 security issues in the Perl core, not for modules independently distributed on
643 The F<Changes> file for an explanation of how to view exhaustive details on
646 The F<INSTALL> file for how to build Perl.
648 The F<README> file for general stuff.
650 The F<Artistic> and F<Copying> files for copyright information.