4 This has been completed up to 8367b6810 except for:
5 747627ec455e0765e07733ece1545aa3f728a00a (Steffen Müller)
6 dd35fa16610ef2fa0d46f5129e626b99cf350d77 (H. Merijn Brand)
7 e64345f82d66a32f6da47acf482e7e6c9282b433 (Steffen Müller)
8 f1d35e3443aa8451bf47be80983076fe28626113 (Karthik Rajagopalan)
12 [ this is a template for a new perldelta file. Any text flagged as
13 XXX needs to be processed before release. ]
15 perldelta - what is new for perl v5.15.2
19 This document describes differences between the 5.15.1 release and
22 If you are upgrading from an earlier release such as 5.15.0, first read
23 L<perl5151delta>, which describes differences between 5.15.0 and
28 XXX Any important notices here
30 =head1 Core Enhancements
32 XXX New core language features go here. Summarise user-visible core language
33 enhancements. Particularly prominent performance optimisations could go
34 here, but most should go in the L</Performance Enhancements> section.
36 [ List each enhancement as a =head2 entry ]
38 =head2 Subroutines in the CORE namespace
40 Many Perl keywords are now available as subroutines in the CORE namespace.
41 These cannot be called through references or via C<&foo> syntax yet, but
42 must be called as barewords. In other words, you can now do this:
44 BEGIN { *entangle = \&CORE::tie }
45 entangle $variable, $package, @args;
47 This currently works for overridable keywords other than C<dump> and the
50 Work is under way to allow these subroutines to be called through
53 =head2 C<__FILE__()> Syntax
55 The C<__FILE__>, C<__LINE__> and C<__PACKAGE__> tokens can now be written
56 with an empty pair of parentheses after them. This makes them parse the
57 same way as C<time>, C<fork> and other built-in functions.
61 XXX Any security-related notices go here. In particular, any security
62 vulnerabilities closed should be noted here rather than in the
63 L</Selected Bug Fixes> section.
65 [ List each security issue as a =head2 entry ]
67 =head1 Incompatible Changes
69 XXX For a release on a stable branch, this section aspires to be:
71 There are no changes intentionally incompatible with 5.XXX.XXX
72 If any exist, they are bugs and reports are welcome.
74 [ List each incompatible change as a =head2 entry ]
76 =head2 C<UNIVERSAL::VERSION> now returns $VERSION
78 C<UNIVERSAL::VERSION> now return whatever is in $VERSION, instead of
79 returning $VERSION converted to a version object and then to a string.
80 As a result, it no longer parses the version when called without arguments,
81 so it no longer dies in that case for malformed versions. This allows
82 custom version number parsers to use C<< ->VERSION >> to retrieve the
83 version number, as was the case in Perl 5.8 [perl #95544].
87 XXX Any deprecated features, syntax, modules etc. should be listed here.
88 In particular, deprecated modules should be listed here even if they are
89 listed as an updated module in the L</Modules and Pragmata> section.
91 [ List each deprecation as a =head2 entry ]
93 =head1 Performance Enhancements
95 XXX Changes which enhance performance without changing behaviour go here. There
96 may well be none in a stable release.
98 [ List each enhancement as a =item entry ]
108 =head1 Modules and Pragmata
110 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
111 go here. If Module::CoreList is updated, generate an initial draft of the
112 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
113 entries to STDOUT. Results can be pasted in place of the '=head2' entries
114 below. A paragraph summary for important changes should then be added by hand.
115 In an ideal world, dual-life modules would have a F<Changes> file that could be
118 [ Within each section, list entries as a =item entry ]
120 =head2 New Modules and Pragmata
130 =head2 Updated Modules and Pragmata
136 L<B> has been upgraded from version 1.30 to version 1.31
138 The XS code has changed slightly, as it was too tightly coupled to
139 the contents of the header F<embedvar.h>. Documentation in L<B::Terse>
140 and L<B::Xref> has been improved, hence their versions have been increased.
144 L<CPAN> has been upgraded from version 1.9600 to version 1.9800
148 L<CPANPLUS> has been upgraded from version 0.9108 to version 0.9109
150 Fixed support for v-strings and x.y.z versions with v5.8.4
154 L<CPAN::Meta> has been upgraded from version 2.110930_001 to version 2.112150
156 Stringify any objects encountered during conversion.
158 Clarified that file paths in the 'provides' section must be in
159 Unix-style (i.e. forward slashes)
163 L<DB_File> has been upgraded from version 1.822 to version 1.824
165 Will now croak if attempt to freeze/thaw DB_File object [RT #69985]
169 L<diagnostics> has been upgraded from version 1.23 to 1.24.
171 It now supports the %u formatting code. Previously it was unable to find
172 descriptions for messages whose entries in L<perldiag> included that code
177 L<Encode> has been upgraded from version 2.43 to version 2.44
179 Addressed 'decode_xs n-byte heap-overflow' security bug in Unicode.xs
183 L<ExtUtils::Install> has been upgraded from version 1.56 to version 1.57.
185 There is no change to ExtUtils::Install other than the version number
186 increase, but L<ExtUtils::Installed> has been upgraded from version 1.999_001
187 to version 1.999002 and a new C<skip_cwd> attribute has been added.
191 L<ExtUtils::MakeMaker> has been upgraded from version 6.58 to version 6.59
195 L<IPC::Open3> has been upgraded from version 1.11 to 1.12.
197 C<open3> with "-" for the program name works once more. This was broken in
198 version 1.06 (and hence in Perl 5.14.0) [perl #95748].
202 L<Module::Build> has been upgraded from version 0.3800 to version 0.39_01.
204 Pod to HTML internals changed to support revisions to Pod::Html in core.
205 Also fixes some minor bugs. [rt.cpan.org #68585] [rt.cpan.org #67893]
210 L<Module::Load> has been upgraded from version 0.18 to version 0.20
214 L<Module::Metadata> has been upgraded from version 1.000004 to version 1.000005
216 Added C<new_from_handle()> method.
220 L<Params::Check> has been upgraded from version 0.28 to version 0.32
224 L<PerlIO::via> has been upgraded from version 0.11 to version 0.12.
226 The only change is a correction in the documentation.
230 L<Term::ANSIColor> has been upgraded from version 3.00 to version 3.01
232 Only interpret an initial array reference as a list of colors, not any initial
233 reference, allowing the colored function to work properly on objects with
234 stringification defined.
238 L<Unicode::Collate> has been upgraded from version 0.77 to version 0.78
242 L<Unicode::Normalize> has been upgraded from version 1.12 to version 1.13
246 =head2 Removed Modules and Pragmata
258 XXX Changes to files in F<pod/> go here. Consider grouping entries by
259 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
261 =head2 New Documentation
263 XXX Changes which create B<new> files in F<pod/> go here.
265 =head3 L<perlexperiment>
267 This document is intended to provide a list of experimental features in
268 Perl. It is still a work in progress.
270 =head2 Changes to Existing Documentation
272 XXX Changes which significantly change existing files in F<pod/> go here.
273 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
282 The ($;) prototype syntax, which has existed for rather a long time, is now
283 documented in L<perlsub>. It allows a unary function to have the same
284 precedence as a list operator.
290 The following additions or changes have been made to diagnostic output,
291 including warnings and fatal error messages. For the complete list of
292 diagnostic messages, see L<perldiag>.
294 XXX New or changed warnings emitted by the core's C<C> code go here. Also
295 include any changes in L<perldiag> that reconcile it to the C<C> code.
297 [ Within each section, list entries as a =item entry that links to perldiag,
302 L<Invalid version object|perldiag/"Invalid version object">
305 =head2 New Diagnostics
307 XXX Newly added diagnostic messages go here
315 L<&CORE::%s cannot be called directly|perldiag/"&CORE::%s cannot be called directly">
317 (F) You tried to call a subroutine in the C<CORE::> namespace
318 with C<&foo> syntax or through a reference. The subroutines
319 in this package cannot yet be called that way, but must be
320 called as barewords. Something like this will work:
322 BEGIN { *shove = \&CORE::push; }
323 shove @array, 1,2,3; # pushes on to @array
333 XXX L<message|perldiag/"message">
337 =head2 Changes to Existing Diagnostics
339 XXX Changes (i.e. rewording) of diagnostic messages go here
345 XXX Describe change here
349 =head1 Utility Changes
351 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
352 here. Most of these are built within the directories F<utils> and F<x2p>.
354 [ List utility changes as a =head3 entry for each utility and =item
355 entries for each change
356 Use L<XXX> with program names to get proper documentation linking. ]
364 Fixed a bug whereby other perls under the current directory could cause
365 false positive failures.
369 Tests for .ph files have been removed, as these test have been optional since
370 2005 and .ph files are no longer generated during installation.
376 See the entry for C<< diagnostics >> in L</Updated Modules and Pragmata>,
379 =head1 Configuration and Compilation
381 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
382 go here. Any other changes to the Perl build process should be listed here.
383 However, any platform-specific changes should be listed in the
384 L</Platform Support> section, instead.
386 [ List changes as a =item entry ].
392 F<makedef.pl> has been refactored. This should have no noticeable affect on
393 any of the platforms that use it as part of their build (AIX, VMS, Win32).
399 XXX Any significant changes to the testing of a freshly built perl should be
400 listed here. Changes which create B<new> files in F<t/> go here as do any
401 large changes to the testing harness (e.g. when parallel testing was added).
402 Changes to existing files in F<t/> aren't worth summarising, although the bugs
403 that they represent may be covered elsewhere.
405 [ List each test improvement as a =item entry ]
415 =head1 Platform Support
417 XXX Any changes to platform support should be listed in the sections below.
419 [ Within the sections, list each platform as a =item entry with specific
420 changes as paragraphs below it. ]
424 =item HP-UX PA-RISC/64 now supports gcc-4.x
426 A fix to correct the socketsize now makes the test suite pass on HP-UX
427 PA-RISC for 64bitall builds.
433 XXX List any platforms that this version of perl compiles on, that previous
434 versions did not. These will either be enabled by new files in the F<hints/>
435 directories, or new subdirectories and F<README> files at the top level of the
440 =item XXX-some-platform
446 =head2 Discontinued Platforms
448 XXX List any platforms that this version of perl no longer compiles on.
452 =item XXX-some-platform
458 =head2 Platform-Specific Notes
460 XXX List any changes for specific platforms. This could include configuration
461 and compilation changes or changes in portability/compatibility. However,
462 changes within modules for platforms should generally be listed in the
463 L</Modules and Pragmata> section.
467 =item XXX-some-platform
473 =head1 Internal Changes
475 XXX Changes which affect the interface available to C<XS> code go here.
476 Other significant internal changes for future core maintainers should
479 [ List each change as a =item entry ]
485 F<embedvar.h> has been simplified, and one level of macro indirection for
486 PL_* variables has been removed for the default (non-multiplicity)
487 configuration. PERLVAR*() macros now directly expand their arguments to
488 tokens such as C<PL_defgv>, instead of expanding to C<PL_Idefgv>, with
489 F<embedvar.h> defining a macro to map C<PL_Idefgv> to C<PL_defgv>. XS code
490 which has unwarranted chumminess with the implementation may need updating.
494 =head1 Selected Bug Fixes
496 XXX Important bug fixes in the core language are summarised here.
497 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
498 L</Modules and Pragmata>.
500 [ List each fix as a =item entry ]
506 Locking a subroutine (via C<lock &sub>) is no longer a compile-time error
507 for regular subs. For lvalue subroutines, it no longer tries to return the
508 sub as a scalar, resulting in strange side effects like C<ref \$_>
509 returning "CODE" in some instances.
511 C<lock &sub> is now a run-time error if L<threads::shared> is loaded (a
512 no-op otherwise), but that may be rectified in a future version.
516 The prototypes of several built-in functions--C<getprotobynumber>, C<lock>,
517 C<not> and C<select>--have been corrected, or at least are now closer to
522 Most dereferencing operators (C<${}>, etc.) used to call C<FETCH> twice on
523 a tied operand when doing a symbolic dereference (looking up a variable by
524 name, which is not permitted under C<use strict 'refs'>). Only C<&{}> did
525 not have this problem. This has been fixed.
529 A minor regression introduced in 5.15.0 has been fixed. Dereferencing a
530 magical mortal (e.g., the return value of C<delete> on a tied hash element)
531 explicitly returned from a subroutine called recursively was not calling
532 C<FETCH>. This would affect code like C<@{ foo() }> where the C<foo> sub
533 contains C<return delete $hash{elem}> and is calling itself.
537 A panic involving the combination of the regular expression modifiers
538 C</aa> and the C<\b> escape sequence introduced in 5.14.0 has been
543 stat() would always return the inode number as an IV, even when the
544 original was unsigned, or too large to fit in an IV. stat() now
545 returns the inode number as the type that would best preserve the
546 original value. [perl #84590]
550 The combination of the regular expression modifiers C</aa> and the C<\b>
551 and C<\B> escape sequences did not work properly on UTF-8 encoded
552 strings. All non-ASCII characters under C</aa> should be treated as
553 non-word characters, but what was happening was that Unicode rules were
554 used to determine wordness/non-wordness for non-ASCII characters. This
555 is now fixed [perl #95968].
559 Infinite loops like C<1 while 1> used to stop C<strict 'subs'> mode from
560 working for the rest of the block.t
564 The C<\h>, C<\H>, C<\v> and C<\V> regular expression metacharacters used to
565 cause a panic error message when attempting to match at the end of the
566 string [perl #96354].
570 For list assignments like C<($a,$b) = ($b,$a)>, Perl has to make a copy of
571 the items on the right-hand side before assignment them to the left. For
572 efficiency's sake, it assigns the values on the right straight to the items
573 on the left no variable is mentioned on both sides, as in
574 C<($a,$b) = ($c,$d)>. The logic for determining when it can cheat was
575 faulty, in that C<&&> and C<||> on the right-hand side could fool it. So
576 C<($a,$b) = $some_true_value && ($b,$a)> would end up assigning the value
577 of C<$b> to both scalars.
581 Perl no longer tries to apply lvalue context to the string in
582 C<("string", $variable) ||= 1> (which used to be an error). Since the
583 left-hand side of C<||=> is evaluated in scalar context, that's a scalar
584 comma operator, which gives all but the last item void context. There is
585 no such thing as void lvalue context, so it was a mistake for Perl to try
586 to force it [perl #96942].
590 =head1 Known Problems
592 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
593 tests that had to be C<TODO>ed for the release would be noted here, unless
594 they were specific to a particular platform (see below).
596 This is a list of some significant unfixed bugs, which are regressions
597 from either 5.XXX.XXX or 5.XXX.XXX.
599 [ List each fix as a =item entry ]
611 XXX If any significant core contributor has died, we've added a short obituary
614 =head1 Acknowledgements
616 XXX Generate this with:
618 perl Porting/acknowledgements.pl v5.15.1..HEAD
620 =head1 Reporting Bugs
622 If you find what you think is a bug, you might check the articles
623 recently posted to the comp.lang.perl.misc newsgroup and the perl
624 bug database at http://rt.perl.org/perlbug/ . There may also be
625 information at http://www.perl.org/ , the Perl Home Page.
627 If you believe you have an unreported bug, please run the L<perlbug>
628 program included with your release. Be sure to trim your bug down
629 to a tiny but sufficient test case. Your bug report, along with the
630 output of C<perl -V>, will be sent off to perlbug@perl.org to be
631 analysed by the Perl porting team.
633 If the bug you are reporting has security implications, which make it
634 inappropriate to send to a publicly archived mailing list, then please send
635 it to perl5-security-report@perl.org. This points to a closed subscription
636 unarchived mailing list, which includes
637 all the core committers, who will be able
638 to help assess the impact of issues, figure out a resolution, and help
639 co-ordinate the release of patches to mitigate or fix the problem across all
640 platforms on which Perl is supported. Please only use this address for
641 security issues in the Perl core, not for modules independently
646 The F<Changes> file for an explanation of how to view exhaustive details
649 The F<INSTALL> file for how to build Perl.
651 The F<README> file for general stuff.
653 The F<Artistic> and F<Copying> files for copyright information.