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<ExtUtils::CBuilder> has been upgraded from version 0.280206 to 0.280208.
127 It no longer fails when trying to embed manifests on Windows
128 [perl #111782, #111798].
132 L<File::DosGlob> has been upgraded from version 1.07 to 1.08.
134 There are no visible changes, only minor internal refactorings.
138 L<File::Spec::Unix> has been upgraded from version 3.39_02 to 3.39_03.
140 C<abs2rel> could produce incorrect results when given two relative paths or
141 the root directory twice [perl #111510].
145 L<IO> has been upgraded from version 1.25_06 to 1.25_07.
147 C<sync()> can now be called on read-only file handles [perl #64772].
151 L<Pod::Html> has been upgraded from version 1.15_02 to 1.16.
153 The option C<--libpods> has been re-instated. It is deprecated, and its use
154 does nothing other than issue a warning that it is no longer supported.
158 L<Unicode::UCD> has been upgraded from version 0.43 to 0.44.
160 This adds a function L<all_casefolds()|Unicode::UCD/all_casefolds()>
161 that returns all the casefolds.
165 =head2 Removed Modules and Pragmata
177 XXX Changes to files in F<pod/> go here. Consider grouping entries by
178 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
180 =head2 New Documentation
182 XXX Changes which create B<new> files in F<pod/> go here.
186 XXX Description of the purpose of the new file here
188 =head2 Changes to Existing Documentation
190 XXX Changes which significantly change existing files in F<pod/> go here.
191 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
200 XXX Description of the change here
206 The following additions or changes have been made to diagnostic output,
207 including warnings and fatal error messages. For the complete list of
208 diagnostic messages, see L<perldiag>.
210 XXX New or changed warnings emitted by the core's C<C> code go here. Also
211 include any changes in L<perldiag> that reconcile it to the C<C> code.
213 [ Within each section, list entries as a =item entry that links to perldiag,
218 L<Invalid version object|perldiag/"Invalid version object">
221 =head2 New Diagnostics
223 XXX Newly added diagnostic messages go here
231 XXX L<message|perldiag/"message">
241 XXX L<message|perldiag/"message">
245 =head2 Changes to Existing Diagnostics
247 XXX Changes (i.e. rewording) of diagnostic messages go here
253 XXX Describe change here
257 =head1 Utility Changes
259 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
260 here. Most of these are built within the directories F<utils> and F<x2p>.
262 [ List utility changes as a =head3 entry for each utility and =item
263 entries for each change
264 Use L<XXX> with program names to get proper documentation linking. ]
276 =head1 Configuration and Compilation
278 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
279 go here. Any other changes to the Perl build process should be listed here.
280 However, any platform-specific changes should be listed in the
281 L</Platform Support> section, instead.
283 [ List changes as a =item entry ].
295 XXX Any significant changes to the testing of a freshly built perl should be
296 listed here. Changes which create B<new> files in F<t/> go here as do any
297 large changes to the testing harness (e.g. when parallel testing was added).
298 Changes to existing files in F<t/> aren't worth summarising, although the bugs
299 that they represent may be covered elsewhere.
301 [ List each test improvement as a =item entry ]
311 =head1 Platform Support
313 XXX Any changes to platform support should be listed in the sections below.
315 [ Within the sections, list each platform as a =item entry with specific
316 changes as paragraphs below it. ]
320 XXX List any platforms that this version of perl compiles on, that previous
321 versions did not. These will either be enabled by new files in the F<hints/>
322 directories, or new subdirectories and F<README> files at the top level of the
327 =item XXX-some-platform
333 =head2 Discontinued Platforms
335 XXX List any platforms that this version of perl no longer compiles on.
339 =item XXX-some-platform
345 =head2 Platform-Specific Notes
347 XXX List any changes for specific platforms. This could include configuration
348 and compilation changes or changes in portability/compatibility. However,
349 changes within modules for platforms should generally be listed in the
350 L</Modules and Pragmata> section.
356 C<link> on Win32 now attempts to set C<$!> to more appropriate values
357 based on the Win32 API error code. [perl #112272]
361 =head1 Internal Changes
363 XXX Changes which affect the interface available to C<XS> code go here.
364 Other significant internal changes for future core maintainers should
367 [ List each change as a =item entry ]
373 The C<study> function was made a no-op in 5.16. It was simply disabled via
374 a C<return> statement; the code was left in place. Now the code supporting
375 what C<study> used to do has been removed.
379 =head1 Selected Bug Fixes
381 XXX Important bug fixes in the core language are summarised here.
382 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
383 L</Modules and Pragmata>.
385 [ List each fix as a =item entry ]
391 Perl now works as well as can be expected on all releases of Unicode so
392 far. In v5.16, it worked on Unicodes 6.0 and 6.1, but there were
393 various bugs for earlier releases; the older the release the more
398 C<vec> no longer produces "uninitialized" warnings in lvalue context
403 An optimisation involving fixed strings in regular expressions could cause
404 a severe performance penalty in edge cases. This has been fixed
409 The "Can't find an opnumber" message that C<prototype> produces when passed
410 a string like "CORE::nonexistent_keyword" is now passes UTF8 and embedded
411 nulls through unchanged [perl #97478].
415 Under threaded perls, a run-time code block in a regular expression could
416 corrupt the package name stored in the op tree, resulting in bad reads
417 in C<caller>, and possibly crashes [perl #113060].
421 =head1 Known Problems
423 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
424 tests that had to be C<TODO>ed for the release would be noted here, unless
425 they were specific to a particular platform (see below).
427 This is a list of some significant unfixed bugs, which are regressions
428 from either 5.XXX.XXX or 5.XXX.XXX.
430 [ List each fix as a =item entry ]
442 XXX If any significant core contributor has died, we've added a short obituary
445 =head1 Acknowledgements
447 XXX Generate this with:
449 perl Porting/acknowledgements.pl v5.17.0..HEAD
451 =head1 Reporting Bugs
453 If you find what you think is a bug, you might check the articles
454 recently posted to the comp.lang.perl.misc newsgroup and the perl
455 bug database at http://rt.perl.org/perlbug/ . There may also be
456 information at http://www.perl.org/ , the Perl Home Page.
458 If you believe you have an unreported bug, please run the L<perlbug>
459 program included with your release. Be sure to trim your bug down
460 to a tiny but sufficient test case. Your bug report, along with the
461 output of C<perl -V>, will be sent off to perlbug@perl.org to be
462 analysed by the Perl porting team.
464 If the bug you are reporting has security implications, which make it
465 inappropriate to send to a publicly archived mailing list, then please send
466 it to perl5-security-report@perl.org. This points to a closed subscription
467 unarchived mailing list, which includes
468 all the core committers, who will be able
469 to help assess the impact of issues, figure out a resolution, and help
470 co-ordinate the release of patches to mitigate or fix the problem across all
471 platforms on which Perl is supported. Please only use this address for
472 security issues in the Perl core, not for modules independently
477 The F<Changes> file for an explanation of how to view exhaustive details
480 The F<INSTALL> file for how to build Perl.
482 The F<README> file for general stuff.
484 The F<Artistic> and F<Copying> files for copyright information.