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.5
12 This document describes differences between the 5.21.4 release and the 5.21.5
15 If you are upgrading from an earlier release such as 5.21.3, first read
16 L<perl5214delta>, which describes differences between 5.21.3 and 5.21.4.
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 New double-diamond operator
32 C<<< <<>>> >>> is like C<< <> >> but uses three-argument C<open> to open
33 each file in @ARGV. So each element of @ARGV is an actual file name, and
34 "|foo" won't be treated as a pipe open.
36 =head2 Perl now supports POSIX 2008 locale currency additions.
38 On platforms that are able to handle POSIX.1-2008, the
40 L<C<POSIX::localeconv()>|perllocale/The localeconv function>
41 includes the international currency fields added by that version of the
42 POSIX standard. These are
44 C<int_n_sep_by_space>,
47 C<int_p_sep_by_space>,
53 =head2 Perl is now compiled with -fstack-protector-strong if available
55 Perl has been compiled with the anti-stack-smashing option
56 C<-fstack-protector> since 5.10.1. Now Perl uses the newer variant
57 called C<-fstack-protector-strong>, if available. (This was added
60 [ List each security issue as a =head2 entry ]
62 =head1 Incompatible Changes
64 XXX For a release on a stable branch, this section aspires to be:
66 There are no changes intentionally incompatible with 5.XXX.XXX
67 If any exist, they are bugs, and we request that you submit a
68 report. See L</Reporting Bugs> below.
70 [ List each incompatible change as a =head2 entry ]
74 XXX Any deprecated features, syntax, modules etc. should be listed here.
76 =head2 Module removals
78 XXX Remove this section if inapplicable.
80 The following modules will be removed from the core distribution in a
81 future release, and will at that time need to be installed from CPAN.
82 Distributions on CPAN which require these modules will need to list them as
85 The core versions of these modules will now issue C<"deprecated">-category
86 warnings to alert you to this fact. To silence these deprecation warnings,
87 install the modules in question from CPAN.
89 Note that these are (with rare exceptions) fine modules that you are encouraged
90 to continue to use. Their disinclusion from core primarily hinges on their
91 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
92 not usually on concerns over their design.
98 XXX Note that deprecated modules should be listed here even if they are listed
99 as an updated module in the L</Modules and Pragmata> section.
103 =head2 Use of multiple /x regexp modifiers
105 It is now deprecated to say something like any of the following:
111 That is, now C<x> should only occur once in any string of contiguous
112 regular expression pattern modifiers. We do not believe there are any
113 occurrences of this in all of CPAN. This is in preparation for a future
114 Perl release having C</xx> mean to allow white-space for readability in
115 bracketed character classes (those enclosed in square brackets:
118 =head1 Performance Enhancements
120 XXX Changes which enhance performance without changing behaviour go here.
121 There may well be none in a stable release.
123 [ List each enhancement as a =item entry ]
129 C<length> is up to 20% faster for non-magical/non-tied scalars containing a
130 string if it is a non-utf8 string or if C<use bytes;> is in scope.
134 Non-magical/non-tied scalars that contain only a floating point value and are
135 on most Perl builds with 64 bit integers now use 8-32 less bytes of memory
140 =head1 Modules and Pragmata
142 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
143 go here. If Module::CoreList is updated, generate an initial draft of the
144 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
145 for important changes should then be added by hand. In an ideal world,
146 dual-life modules would have a F<Changes> file that could be cribbed.
148 [ Within each section, list entries as a =item entry ]
150 =head2 New Modules and Pragmata
160 =head2 Updated Modules and Pragmata
166 L<attributes> has been upgraded from version 0.23 to 0.24.
168 Avoid reading beyond the end of a buffer. [perl #122629]
172 L<B::Deparse> has been upgraded from version 1.28 to 1.29.
174 Parenthesised arrays in lists passed to C<\> are now correctly deparsed
175 with parentheses (e.g., C<\(@a, (@b), @c)> now retains the parentheses
176 around @b), this preserving the flattening behaviour of referenced
177 parenthesised arrays. Formerly, it only worked for one array: C<\(@a)>.
179 C<local our> is now deparsed correctly, with the C<our> included.
181 C<for($foo; !$bar; $baz) {...}> was deparsed without the C<!> (or C<not>).
184 Core keywords that conflict with lexical subroutines are now deparsed with
185 the C<CORE::> prefix.
187 C<foreach state $x (...) {...}> now deparses correctly with C<state> and
190 C<our @array = split(...)> now deparses correctly with C<our> in those
191 cases where the assignment is optimised away.
195 L<DynaLoader> has been upgraded from version 1.26 to 1.27.
197 Remove dl_nonlazy global if unused in Dynaloader. [perl #122926]
201 L<Fcntl> has been upgraded from version 1.12 to 1.13.
203 Add support for the Linux pipe buffer size fcntl() commands.
207 L<Module::CoreList> has been upgraded from version 5.20140920 to 5.20141020.
209 Updated to cover the latest releases of Perl.
213 L<XSLoader> has been upgraded from version 0.17 to 0.18.
215 Allow XSLoader to load modules from a different namespace.
220 =head2 Removed Modules and Pragmata
232 XXX Changes to files in F<pod/> go here. Consider grouping entries by
233 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
235 =head2 New Documentation
237 XXX Changes which create B<new> files in F<pod/> go here.
241 XXX Description of the purpose of the new file here
243 =head2 Changes to Existing Documentation
245 XXX Changes which significantly change existing files in F<pod/> go here.
246 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
255 Clarifications have been added to L<perlrecharclass/Character Ranges>
256 to the effect that Perl guarantees that C<[A-Z]>, C<[a-z]>, C<[0-9]> and
257 any subranges thereof in regular expression bracketed character classes
258 are guaranteed to match exactly what a naive English speaker would
259 expect them to match, even on platforms (such as EBCDIC) where special
260 handling is required to accomplish this.
266 The following additions or changes have been made to diagnostic output,
267 including warnings and fatal error messages. For the complete list of
268 diagnostic messages, see L<perldiag>.
270 XXX New or changed warnings emitted by the core's C<C> code go here. Also
271 include any changes in L<perldiag> that reconcile it to the C<C> code.
273 =head2 New Diagnostics
275 XXX Newly added diagnostic messages go under here, separated into New Errors
284 XXX L<message|perldiag/"message">
294 XXX L<message|perldiag/"message">
298 =head2 Changes to Existing Diagnostics
300 XXX Changes (i.e. rewording) of diagnostic messages go here
306 '"my" variable &foo::bar can't be in a package' has been reworded to say
307 'subroutine' instead of 'variable'.
311 =head1 Utility Changes
313 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
314 Most of these are built within the directory F<utils>.
316 [ List utility changes as a =head2 entry for each utility and =item
317 entries for each change
318 Use L<XXX> with program names to get proper documentation linking. ]
330 =head1 Configuration and Compilation
332 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
333 go here. Any other changes to the Perl build process should be listed here.
334 However, any platform-specific changes should be listed in the
335 L</Platform Support> section, instead.
337 [ List changes as a =item entry ].
349 XXX Any significant changes to the testing of a freshly built perl should be
350 listed here. Changes which create B<new> files in F<t/> go here as do any
351 large changes to the testing harness (e.g. when parallel testing was added).
352 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
353 that they represent may be covered elsewhere.
355 [ List each test improvement as a =item entry ]
365 =head1 Platform Support
367 XXX Any changes to platform support should be listed in the sections below.
369 [ Within the sections, list each platform as a =item entry with specific
370 changes as paragraphs below it. ]
374 XXX List any platforms that this version of perl compiles on, that previous
375 versions did not. These will either be enabled by new files in the F<hints/>
376 directories, or new subdirectories and F<README> files at the top level of the
381 =item XXX-some-platform
387 =head2 Discontinued Platforms
389 XXX List any platforms that this version of perl no longer compiles on.
393 =item XXX-some-platform
399 =head2 Platform-Specific Notes
401 XXX List any changes for specific platforms. This could include configuration
402 and compilation changes or changes in portability/compatibility. However,
403 changes within modules for platforms should generally be listed in the
404 L</Modules and Pragmata> section.
410 Special handling is required on EBCDIC platforms to get C<qr/[i-j]/> to
411 match only C<"i"> and C<"j">, since there are 7 characters between the
412 code points for C<"i"> and C<"j">. This special handling had only been
413 invoked when both ends of the range are literals. Now it is also
414 invoked if any of the C<\N{...}> forms for specifying a character by
415 name or Unicode code point is used instead of a literal. See
416 L<perlrecharclass/Character Ranges>.
420 =head1 Internal Changes
422 XXX Changes which affect the interface available to C<XS> code go here. Other
423 significant internal changes for future core maintainers should be noted as
426 [ List each change as a =item entry ]
432 SVs of type SVt_NV are now bodyless when a build configure and platform allow
433 it, specifically C<sizeof(NV) <= sizeof(IV)>. The bodyless trick is the same one
434 as for IVs since 5.9.2, but for NVs, unlike IVs, is not guarenteed on all
435 platforms and build configurations.
439 The C<$DB::single>, C<$DB::signal> and C<$DB::trace> now have set and
440 get magic that stores their values as IVs and those IVs are used when
441 testing their values in C<pp_dbstate>. This prevents perl from
442 recursing infinity if an overloaded object is assigned to any of those
443 variables. [perl #122445]
447 C<Perl_tmps_grow> which is marked as public API but undocumented has been
448 removed from public API. If you use C<EXTEND_MORTAL> macro in your XS code to
449 preextend the mortal stack, you are unaffected by this change.
453 C<cv_name>, which was introduced in 5.21.4, has been changed incompatibly.
454 It now has a flags field that allows the caller to specify whether the name
455 should be fully qualified. See L<perlapi/cv_name>.
459 Internally Perl no longer uses the C<SVs_PADMY> flag. C<SvPADMY()> now
460 returns a true value for anything not marked PADTMP. C<SVs_PADMY> is now
465 =head1 Selected Bug Fixes
467 XXX Important bug fixes in the core language are summarized here. Bug fixes in
468 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
470 [ List each fix as a =item entry ]
476 Locking and unlocking values via L<Hash::Util> or C<Internals::SvREADONLY>
477 no longer has any affect on values that are read-only to begin. Unlocking
478 such values could result in crashes, hangs or other erratic behaviour.
482 The internal C<looks_like_number> function (which L<Scalar::Util> provides
483 access to) began erroneously to return true for "-e1" in 5.21.4, affecting
484 also C<-'-e1'>. This has been fixed.
488 The flip-flop operator (C<..> in scalar context) would return the same
489 scalar each time, unles the containing subroutine was called recursively.
490 Now it always returns a new scalar. [perl #122829]
494 Some unterminated C<(?(...)...)> constructs in regular expressions would
495 either crash or give erroneous error messages. C</(?(1)/> is one such
500 C<pack "w", $tied> no longer calls FETCH twice.
504 List assignments like C<($x, $z) = (1, $y)> now work correctly if $x and $y
505 have been aliased by C<foreach>.
509 Some patterns including code blocks with syntax errors, such as
510 C</ (?{(^{})/>, would hang or fail assertions on debugging builds. Now
515 An assertion failure when parsing C<sort> with debugging enabled has been
516 fixed. [perl #122771]
520 C<*a = *b; @a = split //, $b[1]> could do a bad read and produce junk
525 =head1 Known Problems
527 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
528 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
529 platform specific bugs also go here.
531 [ List each fix as a =item entry ]
541 =head1 Errata From Previous Releases
547 XXX Add anything here that we forgot to add, or were mistaken about, in
548 the perldelta of a previous release.
554 XXX If any significant core contributor has died, we've added a short obituary
557 =head1 Acknowledgements
559 XXX Generate this with:
561 perl Porting/acknowledgements.pl v5.21.4..HEAD
563 =head1 Reporting Bugs
565 If you find what you think is a bug, you might check the articles recently
566 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
567 https://rt.perl.org/ . There may also be information at
568 http://www.perl.org/ , the Perl Home Page.
570 If you believe you have an unreported bug, please run the L<perlbug> program
571 included with your release. Be sure to trim your bug down to a tiny but
572 sufficient test case. Your bug report, along with the output of C<perl -V>,
573 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
575 If the bug you are reporting has security implications, which make it
576 inappropriate to send to a publicly archived mailing list, then please send it
577 to perl5-security-report@perl.org. This points to a closed subscription
578 unarchived mailing list, which includes all the core committers, who will be
579 able to help assess the impact of issues, figure out a resolution, and help
580 co-ordinate the release of patches to mitigate or fix the problem across all
581 platforms on which Perl is supported. Please only use this address for
582 security issues in the Perl core, not for modules independently distributed on
587 The F<Changes> file for an explanation of how to view exhaustive details on
590 The F<INSTALL> file for how to build Perl.
592 The F<README> file for general stuff.
594 The F<Artistic> and F<Copying> files for copyright information.