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.6
12 This document describes differences between the 5.13.5 release and
15 If you are upgrading from an earlier release such as 5.13.4, first read
16 L<perl5135delta>, which describes differences between 5.13.4 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 ]
31 =head2 C<(?^...)> regex construct added to signify default modifiers
33 A caret (also called a "cirumflex accent") C<"^"> immediately following
34 a C<"(?"> in a regular expression now means that the subexpression is to
35 not inherit the surrounding modifiers such as C</i>, but to revert to the
36 Perl defaults. Any modifiers following the caret override the defaults.
38 The stringification of regular expressions now uses this notation. The
39 main purpose of this is to allow tests that rely on the stringification
40 to not have to change when new modifiers are added. See
41 L<perlre/Extended Patterns>.
43 =head2 C<"d">, C<"l">, and C<"u"> regex modifiers added
45 These modifiers are currently only available within a C<(?...)> construct.
47 The C<"l"> modifier says to compile the regular expression as if it were
48 in the scope of C<use locale>, even if it is not.
50 The C<"u"> modifier currently does nothing.
52 The C<"d"> modifier is used in the scope of C<use locale> to compile the
53 regular expression as if it were not in that scope.
54 See L<perlre/(?dlupimsx-imsx)>.
56 =head2 C<\N{...}> now handles Unicode named character sequences
58 Unicode has a number of named character sequences, in which particular sequences
59 of code points are given names. C<\N{...}> now recognizes these.
62 =head2 New function C<charnames::string_vianame()>
64 This function is a run-time version of C<\N{...}>, returning the string
65 of characters whose Unicode name is its parameter. It can handle
66 Unicode named character sequences, whereas the pre-existing
67 C<charnames::vianame()> cannot, as the latter returns a single code
73 XXX Any security-related notices go here. In particular, any security
74 vulnerabilities closed should be noted here rather than in the
75 L</Selected Bug Fixes> section.
77 [ List each security issue as a =head2 entry ]
79 =head1 Incompatible Changes
81 =head2 Stringification of regexes has changed
83 Default regular expression modifiers are now notated by using
84 C<(?^...)>. Code relying on the old stringification will fail. The
85 purpose of this is so that when new modifiers are added, such code will
86 not have to change (after this one time), as the stringification will
87 automatically incorporate the new modifiers.
89 Code that needs to work properly with both old- and new-style regexes
90 can avoid the whole issue by using (for Perls since 5.9.5):
92 use re qw(regexp_pattern);
93 my ($pat, $mods) = regexp_pattern($re_ref);
95 where C<$re_ref> is a reference to a compiled regular expression. Upon
96 return, C<$mods> will be a string containing all the non-default
97 modifiers used when the regular expression was compiled, and C<$pattern>
100 If the actual stringification is important, or older Perls need to be
101 supported, you can use something like the following:
103 # Accept both old and new-style stringification
104 my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism';
106 And then use C<$modifiers> instead of C<-xism>.
108 =head2 Regular expressions retain their localeness when interpolated
110 Regular expressions compiled under C<"use locale"> now retain this when
111 interpolated into a new regular expression compiled outside a
112 C<"use locale">, and vice-versa.
114 Previously, a regular expression interpolated into another one inherited
115 the localeness of the surrounding one, losing whatever state it
116 originally had. This is considered a bug fix, but may trip up code that
117 has come to rely on the incorrect behavior.
119 [ List each incompatible change as a =head2 entry ]
123 XXX Any deprecated features, syntax, modules etc. should be listed here.
124 In particular, deprecated modules should be listed here even if they are
125 listed as an updated module in the L</Modules and Pragmata> section.
127 [ List each deprecation as a =head2 entry ]
129 =head1 Performance Enhancements
131 XXX Changes which enhance performance without changing behaviour go here. There
132 may well be none in a stable release.
134 [ List each enhancement as a =item entry ]
144 =head1 Modules and Pragmata
146 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
147 go here. If Module::CoreList is updated, generate an initial draft of the
148 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
149 entries to STDOUT. Results can be pasted in place of the '=head2' entries
150 below. A paragraph summary for important changes should then be added by hand.
151 In an ideal world, dual-life modules would have a F<Changes> file that could be
154 [ Within each section, list entries as a =item entry ]
156 =head2 New Modules and Pragmata
166 =head2 Updated Modules and Pragmata
172 C<Carp> has been upgraded from version 1.18 to 1.19.
174 It no longer autovivifies the C<*CORE::GLOBAL::caller> glob, something it
175 started doing in 1.18, which was released with perl 5.13.4
176 L<[perl #78082]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=78082>
180 C<Data::Dumper> has been upgraded from version 2.128 to 2.129.
182 C<Dumpxs> no longer crashes with globs returned by C<*$io_ref>
183 L<[perl #72332]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72332>.
187 C<Digest::MD5> has been upgraded from version 2.40 to 2.50.
189 It is now safe to use this module in combination with threads.
193 C<File::DosGlob> has been upgraded from version 1.02 to 1.03.
195 It allows patterns containing literal parentheses (they no longer need to
196 be escaped). On Windows, it no longer adds an extra F<./> to the file names
197 returned when the pattern is a relative glob with a drive specification,
199 L<[perl #71712]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71712>.
203 C<File::Find> has been upgraded from version 1.17 to 1.18.
205 It improves handling of backslashes on Windows, so that paths such as
206 F<c:\dir\/file> are no longer generated
207 L<[perl #71710]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71710>.
211 C<if> has been upgraded from version 0.05 to 0.06
215 C<IPC::Open3> has been upgraded from version 1.06 to 1.07.
217 The internal C<xclose> routine now knows how to handle file descriptors, as
218 documented, so duplicating STDIN in a child process using its file
220 L<[perl #76474]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71710>.
224 C<Locale::Maketext> has been upgraded from version 1.15 to 1.16.
226 It fixes an infinite loop in C<Locale::Maketext::Guts::_compile()> when
227 working with tainted values
228 (L<CPAN RT #40727|https://rt.cpan.org/Public/Bug/Display.html?id=40727>).
232 C<NEXT> has been upgraded from version 0.64 to 0.65.
236 C<PathTools> has been upgraded from version 3.31_01 to 3.33.
240 C<sigtrap> has been upgraded from version 1.04 to 1.05.
242 It no longer tries to modify read-only arguments when generating a
244 L<[perl #72340]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72340>.
248 C<threads> has been upgrade from version 1.77_03 to 1.81
252 C<Unicode::Collate> has been upgraded from version 0.59 to 0.60
256 C<Unicode::Normalize> has been upgraded from version 1.06 to 1.07
260 =head2 Removed Modules and Pragmata
272 XXX Changes to files in F<pod/> go here. Consider grouping entries by
273 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
275 =head2 New Documentation
277 XXX Changes which create B<new> files in F<pod/> go here.
281 XXX Description of the purpose of the new file here
283 =head2 Changes to Existing Documentation
285 XXX Changes which significantly change existing files in F<pod/> go here.
286 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
295 The documentation for the C<SvTRUE> macro was simply wrong in stating that
296 get-magic is not processed. It has been corrected.
302 The following additions or changes have been made to diagnostic output,
303 including warnings and fatal error messages. For the complete list of
304 diagnostic messages, see L<perldiag>.
306 XXX New or changed warnings emitted by the core's C<C> code go here. Also
307 include any changes in L<perldiag> that reconcile it to the C<C> code.
309 [ Within each section, list entries as a =item entry ]
311 =head2 New Diagnostics
313 XXX Newly added diagnostic messages go here
323 =head2 Changes to Existing Diagnostics
325 XXX Changes (i.e. rewording) of diagnostic messages go here
331 The 'Layer does not match this perl' error message has been replaced with
332 these more helpful messages:
338 PerlIO layer function table size (%d) does not match size expected by this
343 PerlIO layer instance size (%d) does not match size expected by this perl
348 L<[perl #73754]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73754>
352 =head1 Utility Changes
354 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
355 here. Most of these are built within the directories F<utils> and F<x2p>.
357 [ List utility changes as a =head3 entry for each utility and =item
358 entries for each change
359 Use L<XXX> with program names to get proper documentation linking. ]
371 =head1 Configuration and Compilation
373 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
374 go here. Any other changes to the Perl build process should be listed here.
375 However, any platform-specific changes should be listed in the
376 L</Platform Support> section, instead.
378 [ List changes as a =item entry ].
390 XXX Any significant changes to the testing of a freshly built perl should be
391 listed here. Changes which create B<new> files in F<t/> go here as do any
392 large changes to the testing harness (e.g. when parallel testing was added).
393 Changes to existing files in F<t/> aren't worth summarising, although the bugs
394 that they represent may be covered elsewhere.
396 [ List each test improvement as a =item entry ]
406 =head1 Platform Support
408 XXX Any changes to platform support should be listed in the sections below.
410 [ Within the sections, list each platform as a =item entry with specific
411 changes as paragraphs below it. ]
415 XXX List any platforms that this version of perl compiles on, that previous
416 versions did not. These will either be enabled by new files in the F<hints/>
417 directories, or new subdirectories and F<README> files at the top level of the
422 =item XXX-some-platform
428 =head2 Discontinued Platforms
430 XXX List any platforms that this version of perl no longer compiles on.
434 =item XXX-some-platform
440 =head2 Platform-Specific Notes
442 XXX List any changes for specific platforms. This could include configuration
443 and compilation changes or changes in portability/compatibility. However,
444 changes within modules for platforms should generally be listed in the
445 L</Modules and Pragmata> section.
451 Early versions of Mac OS X (Darwin) had buggy implementations of the
452 C<setregid>, C<setreuid>, C<setrgid> and C<setruid> functions, so perl
453 would pretend they did not exist.
455 These functions are now recognised on Mac OS 10.5 (Leopard; Darwin 9) and
456 higher, as they have been fixed
457 L<[perl #72990]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72990>.
461 C<$Config{gccversion}> is now set correctly when perl is built using the
462 mingw64 compiler from L<http://mingw64.org>
463 L<[perl #73754]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=73754>.
467 =head1 Internal Changes
469 XXX Changes which affect the interface available to C<XS> code go here.
470 Other significant internal changes for future core maintainers should
473 [ List each test improvement as a =item entry ]
479 See L</Regular expressions retain their localeness when interpolated>,
484 The C<sv_cmp_flags>, C<sv_cmp_locale_flags>, C<sv_eq_flags> and
485 C<sv_collxfrm_flags> functions have been added. These are like their
486 non-_flags counterparts, but allow one to specify whether get-magic is
489 The C<sv_cmp>, C<sv_cmp_locale>, C<sv_eq> and C<sv_collxfrm> functions have
490 been replaced with wrappers around the new functions.
494 A new C<sv_2bool_flags> function has been added.
496 This is like C<sv_2bool>, but it lets the calling code decide whether
497 get-magic is handled. C<sv_2bool> is now a macro that calls the new
502 A new macro, C<SvTRUE_nomg>, has been added.
504 This is like C<SvTRUE>, except that it does not process magic. It uses the
505 new C<sv_2bool_flags> function.
509 C<sv_catsv_flags> no longer calls C<mg_get> on its second argument (the
510 source string) if the flags passed to it do not include SV_GMAGIC. So it
511 now matches what the documentation says it does.
515 =head1 Selected Bug Fixes
517 XXX Important bug fixes in the core language are summarised here.
518 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
519 L</Modules and Pragmata>.
521 [ List each fix as a =item entry ]
527 A regular expression match in the right-hand side of a global substitution
528 (C<s///g>) that is in the same scope will no longer cause match variables
529 to have the wrong values on subsequent iterations. This can happen when an
530 array or hash subscript is interpolated in the right-hand side, as in
531 C<s|(.)|@a{ print($1), /./ }|g>
532 L<[perl #19078]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=19078>.
536 Constant-folding used to cause
538 $text =~ ( 1 ? /phoo/ : /bear/)
544 at compile time. Now it correctly matches against C<$_>
545 L<[perl #20444]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=20444>.
549 Parsing Perl code (either with string C<eval> or by loading modules) from
550 within a C<UNITCHECK> block no longer causes the interpreter to crash
551 L<[perl #70614]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=70614>.
555 When C<-d> is used on the shebang (C<#!>) line, the debugger now has access
556 to the lines of the main program. In the past, this sometimes worked and
557 sometimes did not, depending on what order things happened to be arranged
559 L<[perl #71806]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=71806>.
563 The C<y///> or C<tr///> operator now calls get-magic (e.g., the C<FETCH>
564 method of a tie) on its left-hand side just once, not twice
565 L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
569 String comparison (C<eq>, C<ne>, C<lt>, C<gt>, C<le>, C<ge> and
570 C<cmp>) and logical not (C<not> and C<!>) operators no longer call magic
571 (e.g., tie methods) twice on their operands
572 L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
574 This bug was introduced in an earlier 5.13 release, and does not affect
579 When a tied (or other magic) variable is used as, or in, a regular
580 expression, it no longer has its C<FETCH> method called twice
581 L<[perl #76814]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=76814>.
583 This bug was introduced in an earlier 5.13 release, and does not affect
588 The C<-C> command line option can now be followed by other options
589 L<[perl #72434]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=72434>.
593 Assigning a glob to a PVLV used to convert it to a plain string. Now it
594 works correctly, and a PVLV can hold a glob. This would happen when a
595 nonexistent hash or array element was passed to a subroutine:
597 sub { $_[0] = *foo }->($hash{key});
598 # $_[0] would have been the string "*main::foo"
600 It also happened when a glob was assigned to, or returned from, an element
601 of a tied array or hash
602 L<[perl #36051]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=36051>.
606 =head1 Known Problems
608 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
609 tests that had to be C<TODO>ed for the release would be noted here, unless
610 they were specific to a particular platform (see below).
612 This is a list of some significant unfixed bugs, which are regressions
613 from either 5.XXX.XXX or 5.XXX.XXX.
615 [ List each fix as a =item entry ]
627 XXX If any significant core contributor has died, we've added a short obituary
636 Fixed a typo in L<perl5135delta> regarding array slices and smart matching
640 =head1 Acknowledgements
642 XXX The list of people to thank goes here.
644 =head1 Reporting Bugs
646 If you find what you think is a bug, you might check the articles
647 recently posted to the comp.lang.perl.misc newsgroup and the perl
648 bug database at http://rt.perl.org/perlbug/ . There may also be
649 information at http://www.perl.org/ , the Perl Home Page.
651 If you believe you have an unreported bug, please run the B<perlbug>
652 program included with your release. Be sure to trim your bug down
653 to a tiny but sufficient test case. Your bug report, along with the
654 output of C<perl -V>, will be sent off to perlbug@perl.org to be
655 analysed by the Perl porting team.
657 If the bug you are reporting has security implications, which make it
658 inappropriate to send to a publicly archived mailing list, then please send
659 it to perl5-security-report@perl.org. This points to a closed subscription
660 unarchived mailing list, which includes all the core committers, who be able
661 to help assess the impact of issues, figure out a resolution, and help
662 co-ordinate the release of patches to mitigate or fix the problem across all
663 platforms on which Perl is supported. Please only use this address for
664 security issues in the Perl core, not for modules independently
669 The F<Changes> file for an explanation of how to view exhaustive details
672 The F<INSTALL> file for how to build Perl.
674 The F<README> file for general stuff.
676 The F<Artistic> and F<Copying> files for copyright information.