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.17.1
12 This document describes differences between the 5.17.0 release and
15 If you are upgrading from an earlier release such as 5.16.0, first read
16 L<perl5170delta>, which describes differences between 5.16.0 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 More CORE:: subs
33 Several more built-in functions have been added as subroutines to the
34 CORE:: namespace, namely, those non-overridable keywords that can be
35 implemented without custom parsers: C<defined>, C<delete>, C<exists>,
36 C<glob>, C<pos>, C<protoytpe>, C<scalar>, C<split>, C<study>, C<undef>,
38 As some of these have prototypes, C<prototype('CORE::...')> has been
39 changed not to make a distinction between overridable and non-overridable
40 keywords. This is to make C<prototype('CORE::pos')> consistent with
41 C<prototype(&CORE::pos)>.
45 XXX Any security-related notices go here. In particular, any security
46 vulnerabilities closed should be noted here rather than in the
47 L</Selected Bug Fixes> section.
49 [ List each security issue as a =head2 entry ]
51 =head1 Incompatible Changes
53 XXX For a release on a stable branch, this section aspires to be:
55 There are no changes intentionally incompatible with 5.XXX.XXX
56 If any exist, they are bugs, and we request that you submit a
57 report. See L</Reporting Bugs> below.
59 =head2 C<\N{BELL}> now refers to U+1F514 instead of U+0007
61 Unicode 6.0 reused the name "BELL" for a different code point than it
62 traditionally had meant. Since Perl v5.14, use of this name still
63 referred to U+0007, but would raise a deprecated warning. Now, "BELL"
64 refers to U+1F514, and the name for U+0007 is "ALERT". All the
65 functions in L<charnames> have been correspondingly updated.
69 XXX Any deprecated features, syntax, modules etc. should be listed here.
70 In particular, deprecated modules should be listed here even if they are
71 listed as an updated module in the L</Modules and Pragmata> section.
73 [ List each deprecation as a =head2 entry ]
75 =head1 Performance Enhancements
77 XXX Changes which enhance performance without changing behaviour go here. There
78 may well be none in a stable release.
80 [ List each enhancement as a =item entry ]
90 =head1 Modules and Pragmata
92 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
93 go here. If Module::CoreList is updated, generate an initial draft of the
94 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
95 entries to STDOUT. Results can be pasted in place of the '=head2' entries
96 below. A paragraph summary for important changes should then be added by hand.
97 In an ideal world, dual-life modules would have a F<Changes> file that could be
100 [ Within each section, list entries as a =item entry ]
102 =head2 New Modules and Pragmata
112 =head2 Updated Modules and Pragmata
118 L<ExtUtils::CBuilder> has been upgraded from version 0.280206 to 0.280208.
120 Manifest files are now correctly embedded for those versions of VC++ which
125 L<B> has been upgraded from version 1.35 to 1.36.
127 C<B::COP::stashlen> has been replaced with C<B::COP::stashoff>.
129 C<B::COP::stashpv> now supports UTF8 package names and embedded nulls.
133 L<ExtUtils::CBuilder> has been upgraded from version 0.280206 to 0.280208.
135 It no longer fails when trying to embed manifests on Windows
136 [perl #111782, #111798].
140 L<File::DosGlob> has been upgraded from version 1.07 to 1.08.
142 There are no visible changes, only minor internal refactorings.
146 L<File::Spec::Unix> has been upgraded from version 3.39_02 to 3.39_03.
148 C<abs2rel> could produce incorrect results when given two relative paths or
149 the root directory twice [perl #111510].
153 L<IO> has been upgraded from version 1.25_06 to 1.25_07.
155 C<sync()> can now be called on read-only file handles [perl #64772].
159 L<Pod::Html> has been upgraded from version 1.15_02 to 1.16.
161 The option C<--libpods> has been re-instated. It is deprecated, and its use
162 does nothing other than issue a warning that it is no longer supported.
166 L<Unicode::UCD> has been upgraded from version 0.43 to 0.44.
168 This adds a function L<all_casefolds()|Unicode::UCD/all_casefolds()>
169 that returns all the casefolds.
173 =head2 Removed Modules and Pragmata
185 XXX Changes to files in F<pod/> go here. Consider grouping entries by
186 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
188 =head2 New Documentation
190 XXX Changes which create B<new> files in F<pod/> go here.
194 XXX Description of the purpose of the new file here
196 =head2 Changes to Existing Documentation
198 XXX Changes which significantly change existing files in F<pod/> go here.
199 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
208 XXX Description of the change here
214 The following additions or changes have been made to diagnostic output,
215 including warnings and fatal error messages. For the complete list of
216 diagnostic messages, see L<perldiag>.
218 XXX New or changed warnings emitted by the core's C<C> code go here. Also
219 include any changes in L<perldiag> that reconcile it to the C<C> code.
221 [ Within each section, list entries as a =item entry that links to perldiag,
226 L<Invalid version object|perldiag/"Invalid version object">
229 =head2 New Diagnostics
231 XXX Newly added diagnostic messages go here
239 XXX L<message|perldiag/"message">
249 XXX L<message|perldiag/"message">
253 =head2 Changes to Existing Diagnostics
255 XXX Changes (i.e. rewording) of diagnostic messages go here
261 XXX Describe change here
265 =head2 Removals of Diagnostics
271 The "Runaway prototype" warning that occurs in bizarre cases has been
272 removed as being unhelpful and inconsistent.
276 The "Not a format reference" error has been removed, as the only case in
277 which it could be triggered was a bug.
281 =head1 Utility Changes
283 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
284 here. Most of these are built within the directories F<utils> and F<x2p>.
286 [ List utility changes as a =head3 entry for each utility and =item
287 entries for each change
288 Use L<XXX> with program names to get proper documentation linking. ]
300 =head1 Configuration and Compilation
302 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
303 go here. Any other changes to the Perl build process should be listed here.
304 However, any platform-specific changes should be listed in the
305 L</Platform Support> section, instead.
307 [ List changes as a =item entry ].
319 XXX Any significant changes to the testing of a freshly built perl should be
320 listed here. Changes which create B<new> files in F<t/> go here as do any
321 large changes to the testing harness (e.g. when parallel testing was added).
322 Changes to existing files in F<t/> aren't worth summarising, although the bugs
323 that they represent may be covered elsewhere.
325 [ List each test improvement as a =item entry ]
335 =head1 Platform Support
337 XXX Any changes to platform support should be listed in the sections below.
339 [ Within the sections, list each platform as a =item entry with specific
340 changes as paragraphs below it. ]
344 XXX List any platforms that this version of perl compiles on, that previous
345 versions did not. These will either be enabled by new files in the F<hints/>
346 directories, or new subdirectories and F<README> files at the top level of the
351 =item XXX-some-platform
357 =head2 Discontinued Platforms
359 XXX List any platforms that this version of perl no longer compiles on.
363 =item XXX-some-platform
369 =head2 Platform-Specific Notes
371 XXX List any changes for specific platforms. This could include configuration
372 and compilation changes or changes in portability/compatibility. However,
373 changes within modules for platforms should generally be listed in the
374 L</Modules and Pragmata> section.
380 C<link> on Win32 now attempts to set C<$!> to more appropriate values
381 based on the Win32 API error code. [perl #112272]
385 =head1 Internal Changes
387 XXX Changes which affect the interface available to C<XS> code go here.
388 Other significant internal changes for future core maintainers should
391 [ List each change as a =item entry ]
397 The C<study> function was made a no-op in 5.16. It was simply disabled via
398 a C<return> statement; the code was left in place. Now the code supporting
399 what C<study> used to do has been removed.
403 Under threaded perls, there is no longer a separate PV allocated for every
404 COP to store its package name (C<< cop->stashpv >>). Instead, there is an
405 offset (C<< cop->stashoff >>) into the new C<PL_stashpad> array, which
406 holds stash pointers.
410 =head1 Selected Bug Fixes
412 XXX Important bug fixes in the core language are summarised here.
413 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
414 L</Modules and Pragmata>.
416 [ List each fix as a =item entry ]
422 Perl now works as well as can be expected on all releases of Unicode so
423 far. In v5.16, it worked on Unicodes 6.0 and 6.1, but there were
424 various bugs for earlier releases; the older the release the more
429 C<vec> no longer produces "uninitialized" warnings in lvalue context
434 An optimisation involving fixed strings in regular expressions could cause
435 a severe performance penalty in edge cases. This has been fixed
440 The "Can't find an opnumber" message that C<prototype> produces when passed
441 a string like "CORE::nonexistent_keyword" is now passes UTF8 and embedded
442 nulls through unchanged [perl #97478].
446 C<prototype> now treats magical variables like C<$1> the same way as
447 non-magical variables when checking for the CORE:: prefix, instead of
448 treating them as subroutine names.
452 Under threaded perls, a run-time code block in a regular expression could
453 corrupt the package name stored in the op tree, resulting in bad reads
454 in C<caller>, and possibly crashes [perl #113060].
458 Referencing a closure prototype (C<\&{$_[1]}> in an attribute handler for a
459 closure) no longer results in a copy of the subroutine (or assertion
460 failures on debugging builds).
464 C<eval '__PACKAGE__'> now returns the right answer on threaded builds if
465 the current package has been assigned over (as in
466 C<*ThisPackage:: = *ThatPackage::>) [perl #78742].
470 If a package is deleted by code that it calls, it is possible for C<caller>
471 to see a stack frame belonging to that deleted package. C<caller> could
472 crash if the stash's memory address was reused for a scalar and a
473 substitution was performed on the same scalar [perl #113486].
477 C<UNIVERSAL::can> no longer treats its first argument differently
478 depending on whether it is a string or number internally.
482 C<open> with "<&" for the mode checks to see whether the third argument is
483 a number, in determining whether to treat it as a file descriptor or a
484 handle name. Magical variables like C<$1> were always failing the numeric
485 check and being treated as handle names.
489 C<warn>'s handling of magical variables (C<$1>, ties) has undergone several
490 fixes. FETCH is only called once now on a tied argument or a tied C<$@>
491 [perl #97480]. Tied variables returning objects that stringify as "" are
492 no longer ignored. A tied C<$@> that happened to return a reference the
493 I<previous> time is was used is no longer ignored.
497 C<warn ""> now treats C<$@> with a number in it the same way, regardless of
498 whether it happened via C<$@=3> or C<$@="3">. It used to ignore the
499 former. Now it appends "\t...caught", as it has always done with
504 Numeric operators on magical variables (e.g., S<C<$1 + 1>>) used to use
505 floating point operations even where integer operations were more appropriate, resulting in loss of accuracy on 64-bit platforms
510 Unary negation no longer treats a string as a number if the string happened
511 to be used as a number some time. So, if $x contains the string "dogs",
512 C<-$x> returns "-dogs" even if C<$y=0+$x> has happened at some point.
516 In Perl 5.14, C<-'-10'> was fixed to return "10", not "+10". But magical
517 variables (C<$1>, ties) were not fixed till now [perl #57706].
521 Unary negation now treats strings consistently, regardless of the internal
526 =head1 Known Problems
528 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
529 tests that had to be C<TODO>ed for the release would be noted here, unless
530 they were specific to a particular platform (see below).
532 This is a list of some significant unfixed bugs, which are regressions
533 from either 5.XXX.XXX or 5.XXX.XXX.
535 [ List each fix as a =item entry ]
547 XXX If any significant core contributor has died, we've added a short obituary
550 =head1 Acknowledgements
552 XXX Generate this with:
554 perl Porting/acknowledgements.pl v5.17.0..HEAD
556 =head1 Reporting Bugs
558 If you find what you think is a bug, you might check the articles
559 recently posted to the comp.lang.perl.misc newsgroup and the perl
560 bug database at http://rt.perl.org/perlbug/ . There may also be
561 information at http://www.perl.org/ , the Perl Home Page.
563 If you believe you have an unreported bug, please run the L<perlbug>
564 program included with your release. Be sure to trim your bug down
565 to a tiny but sufficient test case. Your bug report, along with the
566 output of C<perl -V>, will be sent off to perlbug@perl.org to be
567 analysed by the Perl porting team.
569 If the bug you are reporting has security implications, which make it
570 inappropriate to send to a publicly archived mailing list, then please send
571 it to perl5-security-report@perl.org. This points to a closed subscription
572 unarchived mailing list, which includes
573 all the core committers, who will be able
574 to help assess the impact of issues, figure out a resolution, and help
575 co-ordinate the release of patches to mitigate or fix the problem across all
576 platforms on which Perl is supported. Please only use this address for
577 security issues in the Perl core, not for modules independently
582 The F<Changes> file for an explanation of how to view exhaustive details
585 The F<INSTALL> file for how to build Perl.
587 The F<README> file for general stuff.
589 The F<Artistic> and F<Copying> files for copyright information.