4 ba593ad davem clone() wasn't cloning the whole stack
5 7dc8663 demerphq Hash Function Change - Murmur hash and true per process...
9 [ this is a template for a new perldelta file. Any text flagged as XXX needs
10 to be processed before release. ]
12 perldelta - what is new for perl v5.17.6
16 This document describes differences between the 5.17.5 release and the 5.17.6
19 If you are upgrading from an earlier release such as 5.17.4, first read
20 L<perl5175delta>, which describes differences between 5.17.4 and 5.17.5.
24 XXX Any important notices here
26 =head1 Core Enhancements
28 XXX New core language features go here. Summarize user-visible core language
29 enhancements. Particularly prominent performance optimisations could go
30 here, but most should go in the L</Performance Enhancements> section.
32 [ List each enhancement as a =head2 entry ]
34 =head2 Character name aliases may now include non-Latin1-range characters
36 It is possible to define your own names for characters for use in
37 C<\N{...}>, C<charnames::vianame()>, etc. These names can now be
38 comprised of characters from the whole Unicode range. This allows for
39 names to be in your native language, and not just English. Certain
40 restrictions apply to the characters that may be used (you can't define
41 a name that has punctuation in it, for example). See L<charnames/CUSTOM
44 =head2 New hash function Murmurhash-32 (v3)
46 We have switched perls hash function to use Murmurhash-32 and added build
47 support for several other hash functions. This new function is expected to
48 performance equivalent for shorter strings and is faster, potentially
49 twice as fast, for hashing longer strings.
53 XXX Any security-related notices go here. In particular, any security
54 vulnerabilities closed should be noted here rather than in the
55 L</Selected Bug Fixes> section.
57 [ List each security issue as a =head2 entry ]
59 =head1 Incompatible Changes
61 XXX For a release on a stable branch, this section aspires to be:
63 There are no changes intentionally incompatible with 5.XXX.XXX
64 If any exist, they are bugs, and we request that you submit a
65 report. See L</Reporting Bugs> below.
67 [ List each incompatible change as a =head2 entry ]
69 =head2 An unknown character name in C<\N{...}> is now a syntax error
71 Previously, it warned, and the Unicode REPLACEMENT CHARACTER was
72 substituted. Unicode now recommends that this situation be a syntax
73 error. Also, the previous behavior led to some confusing warnings and
74 behaviors, and since the REPLACEMENT CHARACTER has no use other than as
75 a stand-in for some unknown character, any code that has this problem is
78 =head2 Formerly deprecated characters in C<\N{}> character name aliases are now errors.
80 Since v5.12.0, it has been deprecated to use certain characters in
81 user-defined C<\N{...}> character names. These now cause a syntax
82 error. For example, it is now an error to begin a name with a digit,
85 my $undraftable = "\N{4F}"; # Syntax error!
87 or to have commas anywhere in the name. See L<charnames/CUSTOM ALIASES>
89 =head2 Per process hash randomization
91 The seed used by perls hash function is now random. This means that the
92 order which keys/values will be returned from functions like keys(),
93 values(), and each() will differ from run to run.
95 This change was introduced to make perls hashes more robust to algorithmic
96 complexity attacks and also because we discovered that it exposes hash
97 ordering dependency bugs and make them easier to track down.
99 =head2 PERL_HASH_SEED enviornment variable now takes a hex value
101 PERL_HASH_SEED no longer accepts an integer as a parameter, instead the
102 value is expected to be a binary string encoded in hex. This is to make
103 the infrastructure support hash seeds of arbitrary lengths which might
104 exceed that of an integer. (SipHash uses a 16 byte seed).
106 =head2 Hash::Util::hash_seed() now returns a string
108 Hash::Util::hash_seed() now returns a string instead of an integer. This
109 is to make the infrastructure support hash seeds of arbitrary lengths
110 which might exceed that of an integer. (SipHash uses a 16 byte seed).
112 =head2 Output of PERL_HASH_SEED_DEBUG has been changed
114 The environment variable PERL_HASH_SEED_DEBUG now shows both the hash
115 function perl was built with AND the seed, in hex in use for that process.
116 Code parsing this output, should it exist, must change to accomodate the
117 new format. Example of the new format:
119 $ PERL_HASH_SEED_DEBUG=1 ./perl -e1
120 HASH_FUNCTION = MURMUR3 HASH_SEED = 0x1476bb9f
124 XXX Any deprecated features, syntax, modules etc. should be listed here. In
125 particular, deprecated modules should be listed here even if they are listed as
126 an updated module in the L</Modules and Pragmata> section.
128 [ List each deprecation as a =head2 entry ]
130 =head1 Performance Enhancements
132 XXX Changes which enhance performance without changing behaviour go here.
133 There may well be none in a stable release.
135 [ List each enhancement as a =item entry ]
141 Lists of lexical variable declarations (C<my($x, $y)>) are now optimised
142 down to a single op, and are hence faster than before.
146 A new C preprocessor define NO_TAINT_SUPPORT was added that, if set, disables
147 Perl's taint support altogether. Using the -T or -t command line flags will
148 cause a fatal error. Beware that both core tests as well as many a CPAN
149 distribution's tests will fail with this change. On the upside, it provides
150 a small performance benefit due to reduced branching.
151 Do not enable this unless you know exactly what you are getting yourself into.
155 =head1 Modules and Pragmata
157 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
158 go here. If Module::CoreList is updated, generate an initial draft of the
159 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
160 entries to STDOUT. Results can be pasted in place of the '=head2' entries
161 below. A paragraph summary for important changes should then be added by hand.
162 In an ideal world, dual-life modules would have a F<Changes> file that could be
165 [ Within each section, list entries as a =item entry ]
167 =head2 New Modules and Pragmata
177 =head2 Updated Modules and Pragmata
183 L<Carp> has been upgraded from version 1.27 to 1.28.
185 Carp is no longer confused when C<caller> returns undef for a package that
190 L<CPAN> has been upgraded from version 1.98 to 1.99_51.
194 L<DynaLoader> has been upgraded from version 1.16 to 1.17.
198 L<Env> has been upgraded from version 1.03 to 1.04.
200 Its SPLICE implementation no longer misbehaves in list context.
204 L<Tie::Hash::NamedCapture> has been upgraded from version 0.08 to 0.09.
208 =head2 Removed Modules and Pragmata
220 XXX Changes to files in F<pod/> go here. Consider grouping entries by
221 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
223 =head2 New Documentation
225 XXX Changes which create B<new> files in F<pod/> go here.
229 XXX Description of the purpose of the new file here
231 =head2 Changes to Existing Documentation
233 XXX Changes which significantly change existing files in F<pod/> go here.
234 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
243 C<*foo{NAME}> and C<*foo{PACKAGE}>, which have existed since perl 5.005,
250 The following additions or changes have been made to diagnostic output,
251 including warnings and fatal error messages. For the complete list of
252 diagnostic messages, see L<perldiag>.
254 XXX New or changed warnings emitted by the core's C<C> code go here. Also
255 include any changes in L<perldiag> that reconcile it to the C<C> code.
257 =head2 New Diagnostics
259 XXX Newly added diagnostic messages go under here, separated into New Errors
268 XXX L<message|perldiag/"message">
278 XXX L<message|perldiag/"message">
282 =head2 Changes to Existing Diagnostics
284 XXX Changes (i.e. rewording) of diagnostic messages go here
290 XXX Describe change here
294 =head1 Utility Changes
296 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
297 Most of these are built within the directories F<utils> and F<x2p>.
299 [ List utility changes as a =head3 entry for each utility and =item
300 entries for each change
301 Use L<XXX> with program names to get proper documentation linking. ]
313 =head1 Configuration and Compilation
315 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
316 go here. Any other changes to the Perl build process should be listed here.
317 However, any platform-specific changes should be listed in the
318 L</Platform Support> section, instead.
320 [ List changes as a =item entry ].
332 XXX Any significant changes to the testing of a freshly built perl should be
333 listed here. Changes which create B<new> files in F<t/> go here as do any
334 large changes to the testing harness (e.g. when parallel testing was added).
335 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
336 that they represent may be covered elsewhere.
338 [ List each test improvement as a =item entry ]
348 =head1 Platform Support
350 XXX Any changes to platform support should be listed in the sections below.
352 [ Within the sections, list each platform as a =item entry with specific
353 changes as paragraphs below it. ]
357 XXX List any platforms that this version of perl compiles on, that previous
358 versions did not. These will either be enabled by new files in the F<hints/>
359 directories, or new subdirectories and F<README> files at the top level of the
364 =item XXX-some-platform
370 =head2 Discontinued Platforms
376 Support code relating to EPOC has been removed. EPOC was a family of
377 operating systems developed by Psion for mobile devices. It was the
378 predecessor of Symbian. The port was last updated in April 2002.
382 =head2 Platform-Specific Notes
384 XXX List any changes for specific platforms. This could include configuration
385 and compilation changes or changes in portability/compatibility. However,
386 changes within modules for platforms should generally be listed in the
387 L</Modules and Pragmata> section.
391 =item XXX-some-platform
397 =head1 Internal Changes
399 XXX Changes which affect the interface available to C<XS> code go here. Other
400 significant internal changes for future core maintainers should be noted as
403 [ List each change as a =item entry ]
409 The private Perl_croak_no_modify has had its context parameter removed. It is
410 now has a void prototype. Users of the public API croak_no_modify remain
415 Copy-on-write (shared hash key) scalars are no longer marked read-only.
416 C<SvREADONLY> returns false on such an SV, but C<SvIsCOW> still returns
421 A new op type, C<OP_PADRANGE> has been introduced. The perl peephole
422 optimiser will, where possible, substitute a single padrange op for a
423 pushmark followed by one or more pad ops, and possibly also skipping list
424 and nextstate ops. In addition, the op can carry out the tasks associated
425 with the RHS of a my(...) = @_ assignment, so those ops may be optimised
430 =head1 Selected Bug Fixes
432 XXX Important bug fixes in the core language are summarized here. Bug fixes in
433 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
435 [ List each fix as a =item entry ]
441 Uninitialized warnings mentioning hash elements would only mention the
442 element name if it was not in the first bucket of the hash, due to an
447 A regular expression optimizer bug could cause multiline "^" to behave
448 incorrectly in the presence of line breaks, such that
449 C<"/\n\n" =~ m#\A(?:^/$)#im> would not match [perl #115242].
453 Failed C<fork> in list context no longer currupts the stack.
454 C<@a = (1, 2, fork, 3)> used to gobble up the 2 and assign C<(1, undef, 3)>
455 if the C<fork> call failed.
459 Numerous memory leaks have been fixed, mostly involving tied variables that
460 die, regular expression character classes and code blocks, and syntax
465 Assigning a regular expression (C<${qr//}>) to a variable that happens to
466 hold a floating point number no longer causes assertion failures on
471 Assigning a regular expression to a scalar containing a number no longer
472 causes subsequent nummification to produce random numbers.
476 Assigning a regular expression to a magic variable no longer wipes away the
477 magic. This is a regression from 5.10.
481 Assigning a regular expression to a blessed scalar no longer results in
482 crashes. This is also a regression from 5.10.
486 Regular expression can now be assigned to tied hash and array elements with
487 flattening into strings.
491 Nummifying a regular expression no longer results in an uninitialized
496 Negative array indices no longer cause EXISTS methods of tied variables to
497 be ignored. This is a regression from 5.12.
501 Negative array indices no longer result in crashes on arrays tied to
506 C<$x = "(?{})"; /a++(?{})+$x/x> no longer erroneous produces an error (just
507 a warning, as expected). This was broken in 5.17.1.
511 C<$byte_overload .= $utf8> no longer results in doubly-encoded UTF8 if the
512 left-hand scalar happened to have produced a UTF8 string the last time
513 overloading was invoked.
517 C<goto &sub> now uses the current value of @_, instead of using the array
518 the subroutine was originally called with. This means
519 C<local @_ = (...); goto &sub> now works [perl #43077].
523 If a debugger is invoked recursively, it no longer stomps on its own
524 lexical variables. Formerly under recursion all calls would share the same
525 set of lexical variables [perl #115742].
529 C<*_{ARRAY}> returned from a subroutine no longer spontaneously
534 =head1 Known Problems
536 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
537 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
538 platform specific bugs also go here.
540 [ List each fix as a =item entry ]
552 XXX If any significant core contributor has died, we've added a short obituary
555 =head1 Acknowledgements
557 XXX Generate this with:
559 perl Porting/acknowledgements.pl v5.17.5..HEAD
561 =head1 Reporting Bugs
563 If you find what you think is a bug, you might check the articles recently
564 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
565 http://rt.perl.org/perlbug/ . There may also be information at
566 http://www.perl.org/ , the Perl Home Page.
568 If you believe you have an unreported bug, please run the L<perlbug> program
569 included with your release. Be sure to trim your bug down to a tiny but
570 sufficient test case. Your bug report, along with the output of C<perl -V>,
571 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
573 If the bug you are reporting has security implications, which make it
574 inappropriate to send to a publicly archived mailing list, then please send it
575 to perl5-security-report@perl.org. This points to a closed subscription
576 unarchived mailing list, which includes all the core committers, who will be
577 able to help assess the impact of issues, figure out a resolution, and help
578 co-ordinate the release of patches to mitigate or fix the problem across all
579 platforms on which Perl is supported. Please only use this address for
580 security issues in the Perl core, not for modules independently distributed on
585 The F<Changes> file for an explanation of how to view exhaustive details on
588 The F<INSTALL> file for how to build Perl.
590 The F<README> file for general stuff.
592 The F<Artistic> and F<Copying> files for copyright information.