5 perldelta - what is new for perl v5.26.0
9 This document describes the differences between the 5.24.0 release and the
14 This release includes two updates with widespread effects:
18 =item * C<.> no longer in C<@INC>
20 The current modules, and for the execution of scripts. See the section
21 L<< Removal of the current directory (C<.>) from C<@INC> >> for the full details.
23 =item * C<do> may now warn
25 C<do> now gives a mandatory warning when it fails to load a file which it
26 would have loaded had C<.> been in C<@INC>.
30 =head1 Core Enhancements
32 =head2 New regular expression modifier C</xx>
34 Specifying two C<x> characters to modify a regular expression pattern
35 does everything that a single one does, but additionally TAB and SPACE
36 characters within a bracketed character class are generally ignored and
37 can be added to improve readability, like
38 S<C</[ ^ A-Z d-f p-x ]/xx>>. Details are at
39 L<perlre/E<sol>x and E<sol>xx>.
41 =head2 New Hash Function For 64-bit Builds
43 We have switched to a hybrid hash function to better balance
44 performance for short and long keys.
46 For short keys, 16 bytes and under, we use an optimised variant of
47 One At A Time Hard, and for longer keys we use Siphash 1-3. For very
48 long keys this is a big improvement in performance. For shorter keys
49 there is a modest improvement.
51 =head2 Indented Here-documents
53 This adds a new modifier '~' to here-docs that tells the parser
54 that it should look for /^\s*$DELIM\n/ as the closing delimiter.
56 These syntaxes are all supported:
67 The '~' modifier will strip, from each line in the here-doc, the
68 same whitespace that appears before the delimiter.
70 Newlines will be copied as is, and lines that don't include the
71 proper beginning whitespace will cause perl to croak.
81 prints "Hello there\n" with no leading whitespace.
85 Since time immemorial Perl has, as a last resort, loaded libraries
86 from the current directory. For security reasons this is no longer the
87 case, the C<@INC> variable no longer contains C<.> as its last element
90 If you want to disable this behavior at compile-time build perl with
91 C<-Udefault_inc_excludes_dot> (C<-Ddefault_inc_excludes_dot> being the
94 If you'd like to add C<.> back to C<@INC> at runtime set
95 C<PERL_USE_UNSAFE_INC=1> in the environment before starting
96 perl. Setting it to 1 restores C<.> in the C<@INC> when perl otherwise
99 Various toolchain modules will set C<PERL_USE_UNSAFE_INC=1>
100 themselves. E.g. L<Test::Harness> sets it since loading modules from a
101 relative path is a common idiom in test code. If you find that you
102 have C<.> in C<@INC> on a perl built with default settings it's likely
103 that your code is being invoked by a toolchain module of some sort.
104 =head2 @{^CAPTURE}, %{^CAPTURE}, and %{^CAPTURE_ALL}
106 C<@{^CAPTURE}> exposes the capture buffers of the last match as an
107 array. So C<$1> is C<${^CAPTURE}[0]>. This is a more efficient equivalent
108 to code like C<substr($matched_string,$-[0],$+[0]-$-[0])>, and you don't
109 have to keep track of the C<$matched_string> either. This variable has no
110 single character equivalent. Note like the other regex magic variables
111 the contents of this variable is dynamic, if you wish to store it beyond
112 the lifetime of the match you must copy it to another array.
114 C<%{^CAPTURE}> is the equivalent to C<%+> (ie named captures). Other than
115 being more self documenting there is no difference between the two forms.
117 C<%{^CAPTURE_ALL}> is the equivalent to C<%-> (ie all named captures).
118 Other than being more self documenting there is no difference between the
121 =head2 Unicode 9.0 is now supported
123 A list of changes is at L<http://www.unicode.org/versions/Unicode9.0.0/>.
124 Modules that are shipped with core Perl but not maintained by p5p do not
125 necessarily support Unicode 9.0. L<Unicode::Normalize> does work on 9.0.
127 =head2 Use of C<\p{I<script>}> uses the improved Script_Extensions property
129 Unicode 6.0 introduced an improved form of the Script (C<sc>) property, and
130 called it Script_Extensions (C<scx>). As of now, Perl uses this improved
131 version when a property is specified as just C<\p{I<script>}>. The meaning of
132 compound forms, like C<\p{sc=I<script>}> are unchanged. This should make
133 programs be more accurate when determining if a character is used in a given
134 script, but there is a slight chance of breakage for programs that very
135 specifically needed the old behavior. See L<perlunicode/Scripts>.
137 =head2 Declaring a reference to a variable
139 As an experimental feature, Perl now allows the referencing operator to come
140 after L<C<my()>|perlfunc/my>, L<C<state()>|perlfunc/state>,
141 L<C<our()>|perlfunc/our>, or L<C<local()>|perlfunc/local>. This syntax must
142 be enabled with C<use feature 'declared_refs'>. It is experimental, and will
143 warn by default unless C<no warnings 'experimental::refaliasing'> is in effect.
144 It is intended mainly for use in assignments to references. For example:
146 use experimental 'refaliasing', 'declared_refs';
149 See L<perlref/Assigning to References> for more details.
151 =head2 Perl can now do default collation in UTF-8 locales on platforms
154 Some platforms natively do a reasonable job of collating and sorting in
155 UTF-8 locales. Perl now works with those. For portability and full
156 control, L<Unicode::Collate> is still recommended, but now you may
157 not need to do anything special to get good-enough results, depending on
158 your application. See
159 L<perllocale/Category C<LC_COLLATE>: Collation: Text Comparisons and Sorting>.
161 =head2 Better locale collation of strings containing embedded C<NUL>
164 In locales that have multi-level character weights, these are now
165 ignored at the higher priority ones. There are still some gotchas in
166 some strings, though. See
167 L<perllocale/Collation of strings containing embedded C<NUL> characters>.
169 =head2 Lexical subroutines are no longer experimental
171 Using the C<lexical_subs> feature introduced in v5.18 no longer emits a warning. Existing
172 code that disables the C<experimental::lexical_subs> warning category
173 that the feature previously used will continue to work. The
174 C<lexical_subs> feature has no effect; all Perl code can use lexical
175 subroutines, regardless of what feature declarations are in scope.
177 =head2 C<CORE> subroutines for hash and array functions callable via
180 The hash and array functions in the C<CORE> namespace--C<keys>, C<each>,
181 C<values>, C<push>, C<pop>, C<shift>, C<unshift> and C<splice>--, can now
182 be called with ampersand syntax (C<&CORE::keys(\%hash>) and via reference
183 (C<< my $k = \&CORE::keys; $k-E<gt>(\%hash) >>). Previously they could only be
186 =head2 POSIX::tmpnam() has been removed
188 The fundamentally unsafe C<tmpnam()> interface was deprecated in
189 Perl 5.22.0 and has now been removed. In its place you can use
190 for example the L<File::Temp> interfaces.
192 =head2 require ::Foo::Bar is now illegal.
194 Formerly, C<require ::Foo::Bar> would try to read F</Foo/Bar.pm>. Now any
195 bareword require which starts with a double colon dies instead.
197 =head2 Unescaped literal C<"{"> characters in regular expression
198 patterns are no longer permissible
200 You have to now say something like C<"\{"> or C<"[{]"> to specify to
201 match a LEFT CURLY BRACKET. This will allow future extensions to the
202 language. This restriction is not enforced, nor are there current plans
203 to enforce it, if the C<"{"> is the first character in the pattern.
205 These have been deprecated since v5.16, with a deprecation message
206 displayed starting in v5.22.
208 =head2 Literal control character variable names are no longer permissible
210 A variable name may no longer contain a literal control character under
211 any circumstances. These previously were allowed in single-character
212 names on ASCII platforms, but have been deprecated there since Perl
213 v5.20. This affects things like C<$I<\cT>>, where I<\cT> is a literal
214 control (such as a C<NAK> or C<NEGATIVE ACKNOWLEDGE> character) in the
217 =head2 C<NBSP> is no longer permissible in C<\N{...}>
219 The name of a character may no longer contain non-breaking spaces. It
220 has been deprecated to do so since Perl v5.22.
222 =head2 create a safer utf8_hop() called utf8_hop_safe()
224 Unlike utf8_hop(), utf8_hop_safe() won't navigate before the beginning or after
225 the end of the supplied buffer.
229 =head2 Removal of the current directory (C<.>) from C<@INC>
231 The perl binary includes a default set of paths in C<@INC>. Historically
232 it has also included the current directory (C<.>) as the final entry,
233 unless run with taint mode enabled (C<perl -T>). While convenient, this has
234 security implications: for example, where a script attempts to load an
235 optional module when its current directory is untrusted (such as F</tmp>),
236 it could load and execute code from under that directory.
238 Starting with v5.26.0, C<.> is always removed by default, not just under
239 tainting. This has major implications for installing modules and executing
242 The following new features have been added to help ameliorate these
247 =item * C<Configure -Udefault_inc_excludes_dot>
249 There is a new C<Configure> option, C<default_inc_excludes_dot> (enabled
250 by default) which builds a perl executable without C<.>; unsetting this
251 option using C<-U> reverts perl to the old behaviour. This may fix your
252 path issues but will reintroduce all the security concerns, so don't
253 build a perl executable like this unless you're I<really> confident that
254 such issues are not a concern in your environment.
256 =item * C<$PERL_USE_UNSAFE_INC>
258 There is a new environment variable recognised by the perl interpreter.
259 If this variable has the value C<1> when the perl interpreter starts up,
260 then C<.> will be automatically appended to C<@INC> (except under tainting).
262 This allows you restore the old perl interpreter behaviour on a
263 case-by-case basis. But note that this intended to be a temporary crutch,
264 and this feature will likely be removed in some future perl version.
265 It is currently set by the C<cpan> utility and C<Test::Harness> to
266 ease installation of CPAN modules which have not been updated handle the
267 lack of dot. Once again, don't use this unless you are sure that this
268 will not reintroduce any security concerns.
270 =item * A new mandatory warning issued by C<do>.
272 While it is well-known that C<use> and C<require> use C<@INC> to search
273 for the file to load, many people don't realise that C<do "file"> also
274 searches C<@INC> if the file is a relative path. With the removal of C<.>,
275 a simple C<do "file.pl"> will fail to read in and execute C<file.pl> from
276 the current directory. Since this is commonly expected behaviour, a new
277 mandatory warning is now issued whenever C<do> fails to load a file which
278 it otherwise would have found if dot had been in C<@INC>.
282 Here are some things script and module authors may need to do to make
283 their software work in the new regime.
287 =item * Script authors
289 If the issue is within your own code (rather than within included
290 modules), then you have two main options. Firstly, if you are confident
291 that your script will only be run within a trusted directory (under which
292 you expect to find trusted files and modules), then add C<.> back into the
296 my $dir = "/some/trusted/directory";
297 chdir $dir or die "Can't chdir to $dir: $!\n";
301 use "Foo::Bar"; # may load /some/trusted/directory/Foo/Bar.pm
302 do "config.pl"; # may load /some/trusted/directory/config.pl
304 On the other hand, if your script is intended to be run from within
305 untrusted directories (such as F</tmp>), then your script suddenly failing
306 to load files may be indicative of a security issue. You most likely want
307 to replace any relative paths with full paths; for example,
313 do "$ENV{HOME}/.foo_config.pl"
315 If you are absolutely certain that you want your script to load and
316 execute a file from the current directory, then use a C<./> prefix; for
319 do "./.foo_config.pl"
321 =item * Installing and using CPAN modules
323 If you install a CPAN module using an automatic tool like C<cpan>, then
324 this tool will itself set the C<PERL_USE_UNSAFE_INC> environment variable
325 while building and testing the module, which may be sufficient to install
326 a distribution which hasn't been updated to be dot-aware. If you want to
327 install such a module manually, then you'll need to replace the
328 traditional invocation:
330 perl Makefile.PL && make && make test && make install
334 (export PERL_USE_UNSAFE_INC=1; \
335 perl Makefile.PL && make && make test && make install)
337 Note that this only helps build and install an unfixed module. It's
338 possible for the tests to pass (since they were run under
339 C<PERL_USE_UNSAFE_INC=1>), but for the module itself to fail to perform
340 correctly in production. In this case you may have to temporarily modify
341 your script until such time as fixed version of the module is released.
346 local @INC = (@INC, '.');
347 # assuming read_config() needs '.' in @INC
348 $config = Foo::Bar->read_config();
351 This is only rarely expected to be necessary. Again, if doing this,
352 assess the resultant risks first.
354 =item * Module Authors
356 If you maintain a CPAN distribution, it may need updating to run in
357 a dotless environment. Although C<cpan> and other such tools will
358 currently set the C<PERL_USE_UNSAFE_INC> during module build, this is
359 temporary workaround for the set of modules which rely on C<.> being in
360 C<@INC> for installation and testing, and this may mask deeper issues. It
361 could result in a module which passes tests and installs, but which
364 During build, test and install, it will normally be the case that any perl
365 processes will be executing directly within the root directory of the
366 untarred distribution, or a known subdirectory of that, such as F<t/>. It
367 may well be that F<Makefile.PL> or F<t/foo.t> will attempt to include
368 local modules and configuration files using their direct relative
369 filenames, which will now fail.
371 However, as described above, automatic tools like F<cpan> will (for now)
372 set the C<PERL_USE_UNSAFE_INC> environment variable, which introduces
375 This makes it likely that your existing build and test code will work, but
376 this may mask issues with your code which only manifest when used after
377 install. It is prudent to try and run your build process with that
378 variable explicitly disabled:
379 (export PERL_USE_UNSAFE_INC=0; \
380 perl Makefile.PL && make && make test && make install)
382 This is more likely to show up any potential problems with your module's
383 build process, or even with the module itself. Fixing such issues will
384 ensure both that your module can again be installed manually, and that
385 it will still build once the C<PERL_USE_UNSAFE_INC> crutch goes away.
387 When fixing issues in tests due to the removal of dot from C<@INC>,
388 reinsertion of dot into C<@INC> should be performed with caution, for this
389 too may suppress real errors in your runtime code. You are encouraged
390 wherever possible to apply the aforementioned approaches with explicit
391 absolute/relative paths, or relocate your needed files into a subdirectory
392 and insert that subdirectory into C<@INC> instead.
394 If your runtime code has problems under the dotless C<@INC>, then the comments
395 above on how to fix for script authors will mostly apply here too. Bear in
396 mind though that it is considered bad form for a module to globally add dot to
397 C<@INC>, since it introduces both a security risk and hides issues of
398 accidentally requiring dot in C<@INC>, as explained above.
402 =head2 "Escaped" colons and relative paths in PATH
404 On Unix systems, Perl treats any relative paths in the PATH environment
405 variable as tainted when starting a new process. Previously, it was
406 allowing a backslash to escape a colon (unlike the OS), consequently
407 allowing relative paths to be considered safe if the PATH was set to
408 something like C</\:.>. The check has been fixed to treat C<.> as tainted
411 =head2 C<-Di> switch is now required for PerlIO debugging output
413 Previously PerlIO debugging output would be sent to the file specified
414 by the C<PERLIO_DEBUG> environment variable if perl wasn't running
415 setuid and the C<-T> or C<-t> switches hadn't been parsed yet.
417 If perl performed output at a point where it hadn't yet parsed its
418 switches this could result in perl creating or overwriting the file
419 named by C<PERLIO_DEBUG> even when the C<-T> switch had been supplied.
421 Perl now requires the C<-Di> switch to produce PerlIO debugging
422 output. By default this is written to C<stderr>, but can optionally
423 be redirected to a file by setting the C<PERLIO_DEBUG> environment
426 If perl is running setuid or the C<-T> switch has supplied
427 C<PERLIO_DEBUG> is ignored and the debugging output is sent to
428 C<stderr> as for any other C<-D> switch.
430 =head1 Incompatible Changes
432 =head2 C<${^ENCODING}> has been removed
434 Consequently, the L<encoding> pragma's default mode is no longer supported. If
435 you still need to write your source code in encodings other than UTF-8, use a
436 source filter such as L<Filter::Encoding> on CPAN or L<encoding>'s C<Filter>
439 =head2 C<scalar(%hash)> return signature changed
441 The value returned for C<scalar(%hash)> will no longer show information about
442 the buckets allocated in the hash. It will simply return the count of used
443 keys. It is thus equivalent to C<0+keys(%hash)>.
445 A form of backwards compatibility is provided via C<Hash::Util::bucket_ratio()>
446 which provides the same behavior as C<scalar(%hash)> provided prior to Perl
449 =head2 C<keys> returned from an lvalue subroutine
451 C<keys> returned from an lvalue subroutine can no longer be assigned
454 sub foo : lvalue { keys(%INC) }
456 sub bar : lvalue { keys(@_) }
457 (bar) = 3; # also an error
459 This makes the lvalue sub case consistent with C<(keys %hash) = ...> and
460 C<(keys @_) = ...>, which are also errors. [perl #128187]
464 =head2 String delimiters that aren't stand-alone graphemes are now deprecated
466 In order for Perl to eventually allow string delimiters to be Unicode
467 grapheme clusters (which look like a single character, but may be
468 a sequence of several ones), we have to stop allowing a single char
469 delimiter that isn't a grapheme by itself. These are unlikely to exist
470 in actual code, as they would typically display as attached to the
471 character in front of them.
473 =head1 Performance Enhancements
479 A hash in boolean context is now sometimes faster, e.g.
483 This was already special-cased, but some cases were missed, and even the
484 ones which weren't have been improved.
488 Several other ops may now also be faster in boolean context.
490 =item * New Faster Hash Function on 64 bit builds
492 We use a different hash function for short and long keys. This should
493 improve performance and security, especially for long keys.
495 =item * readline is faster
497 Reading from a file line-by-line with C<readline()> or C<< E<lt>E<gt> >> should
498 now typically be faster due to a better implementation of the code that
499 searches for the next newline character.
503 Reduce cost of SvVALID().
507 C<$ref1 = $ref2> has been optimized.
511 Array and hash assignment are now faster, e.g.
516 especially when the RHS is empty.
520 Reduce the number of odd special cases for the C<SvSCREAM> flag.
524 Avoid sv_catpvn() in do_vop() when unneeded.
528 Enhancements in Regex concat COW implementation.
532 Clearing hashes and arrays has been made slightly faster. Now code
533 like this is around 5% faster:
536 for my $i (1..3_000_000) {
541 and this code around 3% faster:
544 for my $i (1..3_000_000) {
551 Better optimise array and hash assignment
555 Converting a single-digit string to a number is now substantially faster.
559 The internal op implementing the C<split> builtin has been simplified and
560 sped up. Firstly, it no longer requires a subsidiary internal C<pushre> op
561 to do its work. Secondly, code of the form C<my @x = split(...)> is now
562 optimised in the same way as C<@x = split(...)>, and is therefore a few
567 The rather slow implementation for the experimental subroutine signatures
568 feature has been made much faster; it is now comparable in speed with the
569 old-style C<my ($a, $b, @c) = @_>.
573 Bareword constant strings are now permitted to take part in constant
574 folding. They were originally exempted from constant folding in August 1999,
575 during the development of Perl 5.6, to ensure that C<use strict "subs">
576 would still apply to bareword constants. That has now been accomplished a
577 different way, so barewords, like other constants, now gain the performance
578 benefits of constant folding.
580 This also means that void-context warnings on constant expressions of
581 barewords now report the folded constant operand, rather than the operation;
582 this matches the behaviour for non-bareword constants.
586 =head1 Modules and Pragmata
588 =head2 Updated Modules and Pragmata
594 L<Archive::Tar> has been upgraded from version 2.04 to 2.24.
598 L<arybase> has been upgraded from version 0.11 to 0.12.
602 L<attributes> has been upgraded from version 0.27 to 0.29.
604 The deprecation message for the C<:unique> and C<:locked> attributes
605 now mention they will disappear in Perl 5.28.
609 L<B> has been upgraded from version 1.62 to 1.68.
613 L<B::Concise> has been upgraded from version 0.996 to 0.999.
615 Its output is now more descriptive for C<op_private> flags.
619 L<B::Debug> has been upgraded from version 1.23 to 1.24.
623 L<B::Deparse> has been upgraded from version 1.37 to 1.40.
627 L<B::Xref> has been upgraded from version 1.05 to 1.06.
629 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
633 L<base> has been upgraded from version 2.23 to 2.25.
637 L<bignum> has been upgraded from version 0.42 to 0.47.
641 L<Carp> has been upgraded from version 1.40 to 1.42.
645 L<charnames> has been upgraded from version 1.43 to 1.44.
649 L<Compress::Raw::Bzip2> has been upgraded from version 2.069 to 2.074.
653 L<Compress::Raw::Zlib> has been upgraded from version 2.069 to 2.074.
657 L<Config::Perl::V> has been upgraded from version 0.25 to 0.28.
661 L<CPAN> has been upgraded from version 2.11 to 2.18.
665 L<CPAN::Meta> has been upgraded from version 2.150005 to 2.150010.
669 L<Data::Dumper> has been upgraded from version 2.160 to 2.167.
671 The XS implementation now supports Deparse.
673 This fixes a stack management bug. [perl #130487].
677 L<DB_File> has been upgraded from version 1.835 to 1.840.
681 L<Devel::Peek> has been upgraded from version 1.23 to 1.26.
685 L<Devel::PPPort> has been upgraded from version 3.32 to 3.35.
689 L<Devel::SelfStubber> has been upgraded from version 1.05 to 1.06.
691 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
695 L<diagnostics> has been upgraded from version 1.34 to 1.36.
697 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
701 L<Digest> has been upgraded from version 1.17 to 1.17_01.
705 L<Digest::MD5> has been upgraded from version 2.54 to 2.55.
709 L<Digest::SHA> has been upgraded from version 5.95 to 5.96.
713 L<DynaLoader> has been upgraded from version 1.38 to 1.42.
717 L<Encode> has been upgraded from version 2.80 to 2.88.
721 L<encoding> has been upgraded from version 2.17 to 2.19.
723 This module's default mode is no longer supported as of Perl 5.25.3. It now
724 dies when imported, unless the C<Filter> option is being used.
728 L<encoding::warnings> has been upgraded from version 0.12 to 0.13.
730 This module is no longer supported as of Perl 5.25.3. It emits a warning to
731 that effect and then does nothing.
735 L<Errno> has been upgraded from version 1.25 to 1.28.
737 Document that using C<%!> loads Errno for you.
739 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
743 L<ExtUtils::Embed> has been upgraded from version 1.33 to 1.34.
745 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
749 L<ExtUtils::MakeMaker> has been upgraded from version 7.10_01 to 7.24.
753 L<ExtUtils::Miniperl> has been upgraded from version 1.05 to 1.06.
757 L<ExtUtils::ParseXS> has been upgraded from version 3.31 to 3.34.
761 L<ExtUtils::Typemaps> has been upgraded from version 3.31 to 3.34.
765 L<feature> has been upgraded from version 1.42 to 1.47.
767 Fixes the Unicode Bug in the range operator.
771 L<File::Copy> has been upgraded from version 2.31 to 2.32.
775 L<File::Fetch> has been upgraded from version 0.48 to 0.52.
779 L<File::Glob> has been upgraded from version 1.26 to 1.28.
781 Issue a deprecation message for C<File::Glob::glob()>.
785 L<File::Spec> has been upgraded from version 3.63 to 3.67.
789 L<FileHandle> has been upgraded from version 2.02 to 2.03.
793 L<Filter::Simple> has been upgraded from version 0.92 to 0.93.
795 It no longer treats C<no MyFilter> immediately following C<use MyFilter> as
796 end-of-file. [perl #107726]
800 L<Getopt::Long> has been upgraded from version 2.48 to 2.49.
804 L<Getopt::Std> has been upgraded from version 1.11 to 1.12.
808 L<Hash::Util> has been upgraded from version 0.19 to 0.22.
812 L<HTTP::Tiny> has been upgraded from version 0.056 to 0.070.
814 Internal 599-series errors now include the redirect history.
818 L<I18N::LangTags> has been upgraded from version 0.40 to 0.42.
820 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
824 L<IO> has been upgraded from version 1.36 to 1.38.
828 IO-Compress has been upgraded from version 2.069 to 2.074.
832 L<IO::Socket::IP> has been upgraded from version 0.37 to 0.38.
836 L<IPC::Cmd> has been upgraded from version 0.92 to 0.96.
840 L<IPC::SysV> has been upgraded from version 2.06_01 to 2.07.
844 L<JSON::PP> has been upgraded from version 2.27300 to 2.27400_02.
848 L<lib> has been upgraded from version 0.63 to 0.64.
850 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
854 L<List::Util> has been upgraded from version 1.42_02 to 1.46_02.
858 L<Locale::Codes> has been upgraded from version 3.37 to 3.42.
862 L<Locale::Maketext> has been upgraded from version 1.26 to 1.28.
866 L<Locale::Maketext::Simple> has been upgraded from version 0.21 to 0.21_01.
870 L<Math::BigInt> has been upgraded from version 1.999715 to 1.999806.
872 There have also been some core customizations.
876 L<Math::BigInt::FastCalc> has been upgraded from version 0.40 to 0.5005.
880 L<Math::BigRat> has been upgraded from version 0.260802 to 0.2611.
884 L<Math::Complex> has been upgraded from version 1.59 to 1.5901.
888 L<Memoize> has been upgraded from version 1.03 to 1.03_01.
892 L<Module::CoreList> has been upgraded from version 5.20170420 to 5.20170520.
896 L<Module::Load::Conditional> has been upgraded from version 0.64 to 0.68.
900 L<Module::Metadata> has been upgraded from version 1.000031 to 1.000033.
904 L<mro> has been upgraded from version 1.18 to 1.20.
908 L<Net::Ping> has been upgraded from version 2.43 to 2.55.
910 IPv6 addresses and C<AF_INET6> sockets are now supported, along with several
913 Remove sudo from 500_ping_icmp.t.
915 Avoid stderr noise in tests
917 Check for echo in new Net::Ping tests.
921 L<NEXT> has been upgraded from version 0.65 to 0.67.
925 L<Opcode> has been upgraded from version 1.34 to 1.39.
929 L<open> has been upgraded from version 1.10 to 1.11.
933 L<OS2::Process> has been upgraded from version 1.11 to 1.12.
935 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
939 L<overload> has been upgraded from version 1.26 to 1.28.
941 Its compilation speed has been improved slightly.
945 L<parent> has been upgraded from version 0.234 to 0.236.
949 L<perl5db.pl> has been upgraded from version 1.50 to 1.51.
951 Ignore F</dev/tty> on non-Unix systems. [perl #113960]
955 L<Perl::OSType> has been upgraded from version 1.009 to 1.010.
959 L<perlfaq> has been upgraded from version 5.021010 to 5.021011.
963 L<PerlIO> has been upgraded from version 1.09 to 1.10.
967 L<PerlIO::encoding> has been upgraded from version 0.24 to 0.25.
971 L<PerlIO::scalar> has been upgraded from version 0.24 to 0.26.
975 L<Pod::Checker> has been upgraded from version 1.60 to 1.73.
979 L<Pod::Functions> has been upgraded from version 1.10 to 1.11.
983 L<Pod::Html> has been upgraded from version 1.22 to 1.2202.
987 L<Pod::Perldoc> has been upgraded from version 3.25_02 to 3.28.
991 L<Pod::Simple> has been upgraded from version 3.32 to 3.35.
995 L<Pod::Usage> has been upgraded from version 1.68 to 1.69.
999 L<POSIX> has been upgraded from version 1.65 to 1.76. This remedies several
1000 defects in making its symbols exportable. [perl #127821]
1001 The C<POSIX::tmpnam()> interface has been removed,
1002 see L</"POSIX::tmpnam() has been removed">.
1003 Trying to import POSIX subs that have no real implementations
1004 (like C<POSIX::atend()>) now fails at import time, instead of
1005 waiting until runtime.
1009 L<re> has been upgraded from version 0.32 to 0.34
1011 This adds support for the new L<C<E<47>xx>|perlre/E<sol>x and E<sol>xx>
1012 regular expression pattern modifier, and a change to the L<S<C<use re
1013 'strict'>>|re/'strict' mode> experimental feature. When S<C<re
1014 'strict'>> is enabled, a warning now will be generated for all
1015 unescaped uses of the two characters C<}> and C<]> in regular
1016 expression patterns (outside bracketed character classes) that are taken
1017 literally. This brings them more in line with the C<)> character which
1018 is always a metacharacter unless escaped. Being a metacharacter only
1019 sometimes, depending on action at a distance, can lead to silently
1020 having the pattern mean something quite different than was intended,
1021 which the S<C<re 'strict'>> mode is intended to minimize.
1025 L<Safe> has been upgraded from version 2.39 to 2.40.
1029 L<Scalar::Util> has been upgraded from version 1.42_02 to 1.46_02.
1033 L<Storable> has been upgraded from version 2.56 to 2.62.
1035 Fixes [perl #130098].
1039 L<Symbol> has been upgraded from version 1.07 to 1.08.
1043 L<Sys::Syslog> has been upgraded from version 0.33 to 0.35.
1047 L<Term::ANSIColor> has been upgraded from version 4.04 to 4.06.
1051 L<Term::ReadLine> has been upgraded from version 1.15 to 1.16.
1053 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1057 L<Test> has been upgraded from version 1.28 to 1.30.
1059 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1063 L<Test::Harness> has been upgraded from version 3.36 to 3.38.
1067 L<Test::Simple> has been upgraded from version 1.001014 to 1.302073.
1071 L<Thread::Queue> has been upgraded from version 3.09 to 3.12.
1075 L<Thread::Semaphore> has been upgraded from 2.12 to 2.13.
1077 Added the C<down_timed> method.
1081 L<threads> has been upgraded from version 2.07 to 2.15.
1083 Compatibility with 5.8 has been restored.
1085 Fixes [perl #130469].
1089 L<threads::shared> has been upgraded from version 1.51 to 1.56.
1091 This fixes [cpan #119529], [perl #130457]
1095 L<Tie::Hash::NamedCapture> has been upgraded from version 0.09 to 0.10.
1099 L<Time::HiRes> has been upgraded from version 1.9733 to 1.9741.
1101 It now builds on systems with C++11 compilers (such as G++ 6 and Clang++
1104 Now uses C<clockid_t>.
1108 L<Time::Local> has been upgraded from version 1.2300 to 1.25.
1112 L<Unicode::Collate> has been upgraded from version 1.14 to 1.19.
1116 L<Unicode::UCD> has been upgraded from version 0.64 to 0.68.
1118 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1122 L<version> has been upgraded from version 0.9916 to 0.9917.
1126 L<VMS::DCLsym> has been upgraded from version 1.06 to 1.08.
1128 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1132 L<warnings> has been upgraded from version 1.36 to 1.37.
1136 L<XS::Typemap> has been upgraded from version 0.14 to 0.15.
1140 L<XSLoader> has been upgraded from version 0.21 to 0.27.
1142 Fixed a security hole in which binary files could be loaded from a path
1143 outside of L<C<@INC>|perlvar/@INC>.
1145 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1149 =head1 Documentation
1151 =head2 New Documentation
1153 =head3 L<perldeprecation>
1155 This file documents all upcoming deprecations, and some of the deprecations
1156 which already have been removed. The purpose of this documentation is
1157 two-fold: document what will disappear, and by which version, and serve
1158 as a guide for people dealing with code which has features that no longer
1159 work after an upgrade of their perl.
1161 =head2 Changes to Existing Documentation
1169 Use of unassigned code point or non-standalone grapheme for a delimiter will be a fatal error starting in Perl 5.30
1171 This was changed to drop a leading C<v> in C<v5.30>, so it uses the same
1172 style as other deprecation messages.
1176 "\c%c" is more clearly written simply as "%s".
1178 It was decided to undeprecate the use of C<\c%c>, see L<http://www.nntp.perl.org/group/perl.perl5.porters/2017/02/msg242944.html>
1182 Removed redundant C<dSP> from an example.
1186 =head3 L<perlcommunity>
1192 All references to Usenet have been removed.
1202 Updated documentation of C<scalar(%hash)>. See L</scalar(%hash) return
1203 signature changed> above.
1207 Use of single character variables, with the variable name a non printable
1208 character in the range C<\x80>-C<\xFF> is no longer allowed. Update the docs to
1219 All references to Usenet have been removed.
1229 Deprecations are to be marked with a D.
1230 C<"%s() is deprecated on :utf8 handles"> use a deprecation message, and as
1231 such, such be marked C<"(D deprecated)"> and not C<"(W deprecated)">.
1235 =head3 L<perlexperiment>
1241 Documented new feature: See L</Declaring a reference to a variable> above.
1251 Defined on aggregates is no longer allowed. Perlfunc was still reporting it as
1252 deprecated, and that it will be deleted in the future.
1256 Clarified documentation of L<C<seek()>|perlfunc/seek>,
1257 L<C<tell()>|perlfunc/tell> and L<C<sysseek()>|perlfunc/sysseek>.
1258 L<[perl #128607]|https://rt.perl.org/Public/Bug/Display.html?id=128607>
1262 Removed obsolete documentation of L<C<study()>|perlfunc/study>.
1272 Add C<pTHX_> to magic method examples.
1282 Document Tab VS Space.
1286 =head3 L<perlinterp>
1292 L<perlinterp> has been expanded to give a more detailed example of how to
1293 hunt around in the parser for how a given operator is handled.
1297 =head3 L<perllocale>
1303 Document C<NUL> collation handling.
1307 Some locales aren't compatible with Perl. Note the potential bad
1308 consequences of using them.
1312 =head3 L<perlmodinstall>
1318 All references to Usenet have been removed.
1322 =head3 L<perlmodlib>
1328 Updated the mirror list.
1332 All references to Usenet have been removed.
1336 =head3 L<perlnewmod>
1342 All references to Usenet have been removed.
1352 Added a section on calling methods using their fully qualified names.
1356 Do not discourage manual @ISA.
1370 Mention C<Moo> more.
1380 Clarify behavior single quote regexps.
1390 Several minor enhancements to the documentation.
1400 Fixed link to Crosby paper on hash complexity attack.
1410 Documented new feature: See L</Declaring a reference to a variable> above.
1420 Updated documentation of C<scalar(%hash)>. See L</scalar(%hash) return
1421 signature changed> above.
1425 =head3 L<perlunicode>
1431 Documented change to C<\p{I<script>}> to now use the improved Script_Extensions
1432 property. See L</Use of \p{script} uses the improved Script_Extensions
1437 Updated the text to correspond with changes in Unicode UTS#18, concerning
1438 regular expressions, and Perl compatibility with what it says.
1448 Removed obsolete documentation of C<${^ENCODING}>. See L</${^ENCODING} has
1449 been removed> above.
1453 Document C<@ISA>. Was documented other places, not not in L<perlvar>.
1459 =head2 New Diagnostics
1467 Since C<.> is now removed from C<@INC> by default, C<do> will now trigger
1468 a warning recommending to fix the C<do> statement:
1470 L<do "%s" failed, '.' is no longer in @INC|perldiag/do "%s" failed, '.' is no longer in @INC; did you mean do ".E<sol>%s"?>
1474 Using the empty pattern (which re-executes the last successfully-matched
1475 pattern) inside a code block in another regex, as in C</(?{ s!!new! })/>, has
1476 always previously yielded a segfault. It now produces an error:
1477 L<Infinite recursion in regex|perldiag/"Infinite recursion in regex">.
1481 L<The experimental declared_refs feature is not enabled|perldiag/"The experimental declared_refs feature is not enabled">
1483 (F) To declare references to variables, as in C<my \%x>, you must first enable
1486 no warnings "experimental::declared_refs";
1487 use feature "declared_refs";
1491 L<Version control conflict marker|perldiag/"Version control conflict marker">
1493 (F) The parser found a line starting with C<E<lt>E<lt>E<lt>E<lt>E<lt>E<lt>E<lt>>,
1494 C<E<gt>E<gt>E<gt>E<gt>E<gt>E<gt>E<gt>>, or C<=======>. These may be left by a
1495 version control system to mark conflicts after a failed merge operation.
1499 L<%s: command not found|perldiag/"%s: command not found">
1501 (A) You've accidentally run your script through B<bash> or another shell
1502 instead of Perl. Check the #! line, or manually feed your script into
1503 Perl yourself. The #! line at the top of your file could look like:
1509 L<%s: command not found: %s|perldiag/"%s: command not found: %s">
1511 (A) You've accidentally run your script through B<zsh> or another shell
1512 instead of Perl. Check the #! line, or manually feed your script into
1513 Perl yourself. The #! line at the top of your file could look like:
1519 L<Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by S<E<lt>-- HERE> in mE<sol>%sE<sol>|perldiag/"Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by S<<-- HERE> in m/%s/">
1521 Unescaped left braces are already illegal in some contexts in regular
1522 expression patterns, but, due to an oversight, no deprecation warning
1523 was raised in other contexts where they are intended to become illegal.
1524 This warning is now raised in these contexts.
1528 L<Bareword in require contains "%s"|perldiag/"Bareword in require contains "%s"">
1532 L<Bareword in require maps to empty filename|perldiag/"Bareword in require maps to empty filename">
1536 L<Bareword in require maps to disallowed filename "%s"|perldiag/"Bareword in require maps to disallowed filename "%s"">
1540 L<Bareword in require must not start with a double-colon: "%s"|perldiag/"Bareword in require must not start with a double-colon: "%s"">
1550 L<Use of unassigned code point or non-standalone grapheme for a delimiter will be a fatal error starting in Perl 5.30|perldiag/"Use of unassigned code point or non-standalone grapheme for a delimiter will be a fatal error starting in Perl 5.30">
1552 See L</Deprecations>
1556 L<Declaring references is experimental|perldiag/"Declaring references is experimental">
1558 (S experimental::declared_refs) This warning is emitted if you use a reference
1559 constructor on the right-hand side of C<my()>, C<state()>, C<our()>, or
1560 C<local()>. Simply suppress the warning if you want to use the feature, but
1561 know that in doing so you are taking the risk of using an experimental feature
1562 which may change or be removed in a future Perl version:
1564 no warnings "experimental::declared_refs";
1565 use feature "declared_refs";
1570 L<C<${^ENCODING}> is no longer supported. Its use will be fatal in Perl 5.28|perldiag/"${^ENCODING} is no longer supported. Its use will be fatal in Perl 5.28">
1572 (D deprecated) The special variable C<${^ENCODING}>, formerly used to implement
1573 the C<encoding> pragma, is no longer supported as of Perl 5.26.0.
1577 Since C<.> is now removed from C<@INC> by default, C<do> will now trigger
1578 a warning recommending to fix the C<do> statement:
1580 L<do "%s" failed, '.' is no longer in @INC|perldiag/do "%s" failed, '.' is no longer in @INC; did you mean do ".E<sol>%s"?>
1584 =head2 Changes to Existing Diagnostics
1590 When a C<require> fails, we now do not provide C<@INC> when the C<require>
1591 is for a file instead of a module.
1595 When C<@INC> is not scanned for a C<require> call, we no longer display
1596 C<@INC> to avoid confusion.
1600 Attribute "locked" is deprecated, and will disappear in Perl 5.28
1604 Attribute "unique" is deprecated, and will disappear in Perl 5.28
1608 Constants from lexical variables potentially modified elsewhere are
1609 deprecated. This will not be allowed in Perl 5.32
1613 Deprecated use of my() in false conditional. This will be a fatal error
1618 dump() better written as CORE::dump(). dump() will no longer be available
1623 ${^ENCODING} is no longer supported. Its use will be fatal in Perl 5.28
1627 File::Glob::glob() will disappear in perl 5.30. Use File::Glob::bsd_glob()
1632 %s() is deprecated on :utf8 handles. This will be a fatal error in Perl 5.30
1636 $* is no longer supported. Its use will be fatal in Perl 5.30
1640 $* is no longer supported. Its use will be fatal in Perl 5.30
1644 Opening dirhandle %s also as a file. This will be a fatal error in Perl 5.28
1648 Opening filehandle %s also as a directory. This will be a fatal
1653 Setting $/ to a reference to %s as a form of slurp is deprecated,
1654 treating as undef. This will be fatal in Perl 5.28
1658 Unescaped left brace in regex is deprecated here (and will be fatal
1659 in Perl 5.30), passed through in regex; marked by S<< E<lt>-- HERE >> in m/%s/
1663 Unknown charname '' is deprecated. Its use will be fatal in Perl 5.28
1667 Use of bare E<lt>E<lt> to mean E<lt>E<lt>"" is deprecated. Its use will be fatal in Perl 5.28
1671 Use of code point 0x%s is deprecated; the permissible max is 0x%s.
1672 This will be fatal in Perl 5.28
1676 Use of comma-less variable list is deprecated. Its use will be fatal
1681 Use of inherited AUTOLOAD for non-method %s() is deprecated. This
1682 will be fatal in Perl 5.28
1686 Use of strings with code points over 0xFF as arguments to %s operator
1687 is deprecated. This will be a fatal error in Perl 5.28
1691 Improve error for missing tie() package/method. This brings the error messages
1692 in line with the ones used for normal method calls, despite not using
1697 Make the sysread()/syswrite/() etc :utf8 handle warnings default. These
1698 warnings were under 'deprecated' previously.
1702 'do' errors now refer to 'do' (not 'require').
1706 Details as to the exact problem have been added to the diagnostics that
1707 occur when malformed UTF-8 is encountered when trying to convert to a
1712 Executing C<undef $x> where C<$x> is tied or magical no longer incorrectly
1713 blames the variable for an uninitialized-value warning encountered by the
1718 L<Unescaped left brace in regex is illegal here in regex; marked by S<E<lt>-- HERE> in mE<sol>%sE<sol>|perldiag/"Unescaped left brace in regex is illegal here in regex; marked by S<<-- HERE> in m/%s/">
1720 The word "here" has been added to the message that was raised in
1721 v5.25.1. This is to indicate that there are contexts in which unescaped
1722 left braces are not (yet) illegal.
1726 Code like C<$x = $x . "a"> was incorrectly failing to yield a
1727 L<use of uninitialized value|perldiag/"Use of uninitialized value%s">
1728 warning when C<$x> was a lexical variable with an undefined value. That has
1729 now been fixed. [perl #127877]
1733 When the error "Experimental push on scalar is now forbidden" is raised for
1734 the hash functions C<keys>, C<each>, and C<values>, it is now followed by
1735 the more helpful message, "Type of arg 1 to whatever must be hash or
1736 array". [perl #127976]
1740 C<undef *_; shift> or C<undef *_; pop> inside a subroutine, with no
1741 argument to C<shift> or C<pop>, began crashing in Perl 5.14.0, but has now
1746 C<< "string$scalar-E<gt>$*" >> now correctly prefers concat overloading to
1747 string overloading if C<< $scalar-E<gt>$* >> returns an overloaded object,
1748 bringing it into consistency with C<$$scalar>.
1752 C<< /@0{0*-E<gt>@*/*0 >> and similar contortions used to crash, but no longer
1753 do, but merely produce a syntax error. [perl #128171]
1757 C<do> or C<require> with a reference or typeglob which, when stringified,
1758 contains a null character started crashing in Perl 5.20.0, but has now been
1759 fixed. [perl #128182]
1763 =head1 Utility Changes
1765 =head2 F<c2ph> and F<pstruct>
1771 These old utilities have long since superceded by L<h2xs>, and are
1772 now gone from the distribution.
1776 =head2 F<Porting/pod_lib.pl>
1782 Removed spurious executable bit.
1786 Account for possibility of DOS file endings.
1790 =head2 F<Porting/sync-with-cpan>
1800 =head2 F<perf/benchmarks>
1806 Tidy file, rename some symbols.
1810 =head2 F<Porting/checkAUTHORS.pl>
1816 Replace obscure character range with \w.
1820 =head2 F<t/porting/regen.t>
1826 try to be more helpful when tests fail.
1830 =head2 F<utils/h2xs.PL>
1836 Avoid infinite loop for enums.
1846 Long lines in the message body are now wrapped at 900 characters, to stay
1847 well within the 1000-character limit imposed by SMTP mail transfer agents.
1848 This is particularly likely to be important for the list of arguments to
1849 C<Configure>, which can readily exceed the limit if, for example, it names
1850 several non-default installation paths. This change also adds the first unit
1851 tests for perlbug. [perl #128020]
1855 =head1 Configuration and Compilation
1861 C<-Ddefault_inc_excludes_dot> has been turned on by default.
1865 The C<dtrace> build process has further changes:
1871 If the C<-xnolibs> is available, use that so a F<dtrace> perl can be
1872 built within a FreeBSD jail.
1876 On systems that build a dtrace object file (FreeBSD, Solaris and
1877 SystemTap's dtrace emulation), copy the input objects to a separate
1878 directory and process them there, and use those objects in the link,
1879 since C<dtrace -G> also modifies these objects.
1883 Add libelf to the build on FreeBSD 10.x, since dtrace adds references
1888 Generate a dummy dtrace_main.o if C<dtrace -G> fails to build it. A
1889 default build on Solaris generates probes from the unused inline
1890 functions, while they don't on FreeBSD, which causes C<dtrace -G> to
1899 You can now disable perl's use of the PERL_HASH_SEED and
1900 PERL_PERTURB_KEYS environment variables by configuring perl with
1901 C<-Accflags=NO_PERL_HASH_ENV>.
1905 You can now disable perl's use of the PERL_HASH_SEED_DEBUG environment
1906 variable by configuring perl with
1907 C<-Accflags=-DNO_PERL_HASH_SEED_DEBUG>.
1911 Zero out the alignment bytes when calculating the bytes for 80-bit C<NaN>
1912 and C<Inf> to make builds more reproducible. [perl #130133]
1916 Since 5.18 for testing purposes we have included support for
1917 building perl with a variety of non-standard, and non-recommended
1918 hash functions. Since we do not recommend the use of these functions
1919 we have removed them and their corresponding build options. Specifically
1920 this includes the following build options:
1924 PERL_HASH_FUNC_SUPERFAST
1925 PERL_HASH_FUNC_MURMUR3
1926 PERL_HASH_FUNC_ONE_AT_A_TIME
1927 PERL_HASH_FUNC_ONE_AT_A_TIME_OLD
1928 PERL_HASH_FUNC_MURMUR_HASH_64A
1929 PERL_HASH_FUNC_MURMUR_HASH_64B
1933 Remove "Warning: perl appears in your path"
1935 This install warning is more or less obsolete, since most platforms already
1936 *will* have a /usr/bin/perl or similar provided by the OS.
1940 Reduce verbosity of "make install.man"
1942 Previously, two progress messages were emitted for each manpage: one by
1943 installman itself, and one by the function in install_lib.pl that it calls to
1944 actually install the file. Disabling the second of those in each case saves
1945 over 750 lines of unhelpful output.
1949 Cleanup for clang -Weverything support. [perl 129961]
1953 Configure: signbit scan was assuming too much, stop assuming negative 0.
1957 Various compiler warnings have been silenced.
1961 Several smaller changes have been made to remove impediments to compiling under
1966 Builds using C<USE_PAD_RESET> now work again; this configuration had
1971 A probe for C<gai_strerror> was added to F<Configure> that checks if the
1972 the gai_strerror() routine is available and can be used to
1973 translate error codes returned by getaddrinfo() into human
1978 F<Configure> now aborts if both "-Duselongdouble" and "-Dusequadmath" are
1980 L<[perl #126203]|https://rt.perl.org/Public/Bug/Display.html?id=126203>
1984 Fixed a bug in which F<Configure> could append "-quadmath" to the archname even
1985 if it was already present.
1986 L<[perl #128538]|https://rt.perl.org/Public/Bug/Display.html?id=128538>
1990 Clang builds with "-DPERL_GLOBAL_STRUCT" or "-DPERL_GLOBAL_STRUCT_PRIVATE" have
1991 been fixed (by disabling Thread Safety Analysis for these configurations).
1995 F<make_ext.pl> no longer updates a module's F<pm_to_blib> file when no
1996 files require updates. This could cause dependencies, F<perlmain.c>
1997 in particular, to be rebuilt unnecessarily. [perl #126710]
2001 The output of C<perl -V> has been reformatted so that each configuration
2002 and compile-time option is now listed one per line, to improve
2007 C<Configure> now builds C<miniperl> and C<generate_uudmap> if you
2008 invoke it with C<-Dusecrosscompiler> but not C<-Dtargethost=somehost>.
2009 This means you can supply your target platform C<config.sh>, generate
2010 the headers and proceed to build your cross-target perl. [perl #127234]
2014 Builds with C<-Accflags=-DPERL_TRACE_OPS> now only dump the operator
2015 counts when the environment variable C<PERL_TRACE_OPS> to be set to a
2016 non-zero integer. This allows C<make test> to pass on such a build.
2020 When building with GCC 6 and link-time optimization (the C<-flto> option to
2021 C<gcc>), C<Configure> was treating all probed symbols as present on the
2022 system, regardless of whether they actually exist. This has been fixed.
2027 The F<t/test.pl> library is used for internal testing of Perl itself, and
2028 also copied by several CPAN modules. Some of those modules must work on
2029 older versions of Perl, so F<t/test.pl> must in turn avoid newer Perl
2030 features. Compatibility with Perl 5.8 was inadvertently removed some time
2031 ago; it has now been restored. [perl #128052]
2035 The build process no longer emits an extra blank line before building each
2036 "simple" extension (those with only F<*.pm> and F<*.pod> files).
2046 F<XS-APItest/t/utf8.t>: Several small fixes and enhancements.
2050 Tests for locales were erroneously using locales incompatible with Perl.
2054 Some parts of the test suite that try to exhaustively test edge cases in the
2055 regex implementation have been restricted to running for a maximum of five
2056 minutes. On slow systems they could otherwise take several hours, without
2057 significantly improving our understanding of the correctness of the code
2060 In addition, some of those test cases have been split into more files, to
2061 allow them to be run in parallel on suitable systems.
2065 A new internal facility allows analysing the time taken by the individual
2066 tests in Perl's own test suite; see F<Porting/harness-timer-report.pl>.
2070 F<t/re/regexp_nonull.t> has been added to test that the regular expression
2071 engine can handle scalars that do not have a null byte just past the end of
2076 A new test script, F<t/op/decl-refs.t>, has been added to test the new feature,
2077 "Declaring a reference to a variable".
2081 A new test script, F<t/re/anyof.t>, has been added to test that the ANYOF nodes
2082 generated by bracketed character classes are as expected.
2086 F<t/harness> now tries really hard not to run tests outside of the Perl
2087 source tree. [perl #124050]
2091 =head1 Platform Support
2093 =head2 New Platforms
2099 Perl now compiles under NetBSD on VAX machines. However, it's not
2100 possible for that platform to implement floating-point infinities and
2101 NaNs compatibly with most modern systems, which implement the IEEE-754
2102 floating point standard. The hexadecimal floating point (C<0x...p[+-]n>
2103 literals, C<printf %a>) is not implemented, either.
2104 The C<make test> passes 98% of tests.
2110 Test fixes and minor updates.
2114 Account for lack of C<inf>, C<nan>, and C<-0.0> support.
2120 =head2 Platform-Specific Notes
2126 don't treat -Dprefix=/usr as special, instead require an extra option
2127 -Ddarwin_distribution to produce the same results.
2131 Finish removing POSIX deprecated functions.
2135 OS X El Capitan doesn't implement the clock_gettime() or clock_getres() APIs,
2136 emulate them as necessary.
2140 Deprecated syscall(2) on macOS 10.12.
2144 Several tests have been updated to work (or be skipped) on EBCDIC platforms.
2148 L<Net::Ping> UDP test is skipped on HP-UX.
2152 The hints for Hurd have been improved enabling malloc wrap and reporting the
2153 GNU libc used (previously it was an empty string when reported).
2157 VAX floating point formats are now supported.
2165 The path separator for the C<PERL5LIB> and C<PERLLIB> environment entries is
2166 now a colon (C<:>) when running under a Unix shell. There is no change when
2167 running under DCL (it's still C<|>).
2171 Remove some VMS-specific hacks from C<showlex.t>. These were added 15 years
2172 ago, and are no longer necessary for any VMS version now supported.
2176 Move C<_pDEPTH> and C<_aDEPTH> after F<config.h> otherwise DEBUGGING
2177 may not be defined yet.
2181 VAXC has not been a possibility for a good long while, and the versions of the
2182 DEC/Compaq/HP/VSI C compiler that report themselves as "DEC" in a listing file
2183 are 15 years or more out-of-date and can be safely desupported.
2193 Support for compiling perl on Windows using Microsoft Visual Studio 2015
2194 (containing Visual C++ 14.0) has been added.
2196 This version of VC++ includes a completely rewritten C run-time library, some
2197 of the changes in which mean that work done to resolve a socket close() bug in
2198 perl #120091 and perl #118059 is not workable in its current state with this
2199 version of VC++. Therefore, we have effectively reverted that bug fix for
2200 VS2015 onwards on the basis that being able to build with VS2015 onwards is
2201 more important than keeping the bug fix. We may revisit this in the future to
2202 attempt to fix the bug again in a way that is compatible with VS2015.
2204 These changes do not affect compilation with GCC or with Visual Studio versions
2205 up to and including VS2013, i.e. the bug fix is retained (unchanged) for those
2208 Note that you may experience compatibility problems if you mix a perl built
2209 with GCC or VS E<lt>= VS2013 with XS modules built with VS2015, or if you mix a
2210 perl built with VS2015 with XS modules built with GCC or VS E<lt>= VS2013.
2211 Some incompatibility may arise because of the bug fix that has been reverted
2212 for VS2015 builds of perl, but there may well be incompatibility anyway because
2213 of the rewritten CRT in VS2015 (e.g. see discussion at
2214 http://stackoverflow.com/questions/30412951).
2224 Tweaks for Win32 VC vs GCC detection makefile code. This fixes issue that CCHOME
2225 depends on CCTYPE, which in auto detect mode is set after CCHOME, so CCHOME uses
2226 the uninit CCTYPE var. Also fix else vs .ELSE in makefile.mk
2230 fp definitions have been updated.
2236 Fix some breakage, add 'undef' value for default_inc_excludes_dot in build
2241 Drop support for Linux a.out Linux has used ELF for over twenty years.
2245 OpenBSD 6 still does not support returning pid, gid or uid with SA_SIGINFO.
2246 Make sure this is accounted for.
2250 t/uni/overload.t: Skip hanging test on FreeBSD.
2254 =head1 Internal Changes
2260 The C<op_class()> API function has been added. This is like the existing
2261 C<OP_CLASS()> macro, but can more accurately determine what struct an op
2262 has been allocated as. For example C<OP_CLASS()> might return
2263 C<OA_BASEOP_OR_UNOP> indicating that ops of this type are usually
2264 allocated as an C<OP> or C<UNOP>; while C<op_class()> will return
2265 C<OPclass_BASEOP> or C<OPclass_UNOP> as appropriate.
2269 The output format of the C<op_dump()> function (as used by C<perl -Dx>)
2270 has changed: it now displays an "ASCII-art" tree structure, and shows more
2271 low-level details about each op, such as its address and class.
2275 New versions of macros like C<isALPHA_utf8> and C<toLOWER_utf8> have
2276 been added, each with the
2277 suffix C<_safe>, like C<isSPACE_utf8_safe>. These take an extra
2278 parameter, giving an upper limit of how far into the string it is safe
2279 to read. Using the old versions could cause attempts to read beyond the
2280 end of the input buffer if the UTF-8 is not well-formed, and their use
2281 now raises a deprecation warning. Details are at
2282 L<perlapi/Character classification>.
2286 Calling macros like C<isALPHA_utf8> on malformed UTF-8 have issued a
2287 deprecation warning since Perl v5.18. They now die.
2288 Similarly, macros like C<toLOWER_utf8> on malformed UTF-8 now die.
2292 Calling the functions C<utf8n_to_uvchr> and its derivatives, while
2293 passing a string length of 0 is now asserted against in DEBUGGING
2294 builds, and otherwise returns the Unicode REPLACEMENT CHARACTER. If
2295 you have nothing to decode, you shouldn't call the decode function.
2299 The functions C<utf8n_to_uvchr> and its derivatives now return the
2300 Unicode REPLACEMENT CHARACTER if called with UTF-8 that has the overlong
2301 malformation, and that malformation is allowed by the input parameters.
2302 This malformation is where the UTF-8 looks valid syntactically, but
2303 there is a shorter sequence that yields the same code point. This has
2304 been forbidden since Unicode version 3.1.
2308 The functions C<utf8n_to_uvchr> and its derivatives now accept an input
2309 flag to allow the overflow malformation. This malformation is when the
2310 UTF-8 may be syntactically valid, but the code point it represents is
2311 not capable of being represented in the word length on the platform.
2312 What "allowed" means in this case is that the function doesn't return an
2313 error, and advances the parse pointer to beyond the UTF-8 in question,
2314 but it returns the Unicode REPLACEMENT CHARACTER as the value of the
2315 code point (since the real value is not representable).
2319 The C<PADOFFSET> type has changed from being unsigned to signed, and
2320 several pad-related variables such as C<PL_padix> have changed from being
2321 of type C<I32> to type C<PADOFFSET>.
2325 The function C<L<perlapi/utf8n_to_uvchr>> has been changed to not
2326 abandon searching for other malformations when the first one is
2327 encountered. A call to it thus can generate multiple diagnostics,
2328 instead of just one.
2332 A new function, C<L<perlapi/utf8n_to_uvchr_error>>, has been added for
2333 use by modules that need to know the details of UTF-8 malformations
2334 beyond pass/fail. Previously, the only ways to know why a sequence was
2335 ill-formed was to capture and parse the generated diagnostics, or to do
2340 Several new functions for handling Unicode have been added to the API:
2341 C<L<perlapi/is_strict_utf8_string>>,
2342 C<L<perlapi/is_c9strict_utf8_string>>,
2343 C<L<perlapi/is_utf8_string_flags>>,
2344 C<L<perlapi/is_strict_utf8_string_loc>>,
2345 C<L<perlapi/is_strict_utf8_string_loclen>>,
2346 C<L<perlapi/is_c9strict_utf8_string_loc>>,
2347 C<L<perlapi/is_c9strict_utf8_string_loclen>>,
2348 C<L<perlapi/is_utf8_string_loc_flags>>,
2349 C<L<perlapi/is_utf8_string_loclen_flags>>,
2350 C<L<perlapi/is_utf8_fixed_width_buf_flags>>,
2351 C<L<perlapi/is_utf8_fixed_width_buf_loc_flags>>,
2352 C<L<perlapi/is_utf8_fixed_width_buf_loclen_flags>>.
2354 These functions are all extensions of the C<is_utf8_string_*()> functions,
2355 that apply various restrictions to the UTF-8 recognized as valid.
2359 A new API function C<sv_setvpv_bufsize()> allows simultaneously setting the
2360 length and allocated size of the buffer in an C<SV>, growing the buffer if
2365 A new API macro C<SvPVCLEAR()> sets its C<SV> argument to an empty string,
2366 like Perl-space C<$x = ''>, but with several optimisations.
2370 All parts of the internals now agree that the C<sassign> op is a C<BINOP>;
2371 previously it was listed as a C<BASEOP> in F<regen/opcodes>, which meant
2372 that several parts of the internals had to be special-cased to accommodate
2373 it. This oddity's original motivation was to handle code like C<$x ||= 1>;
2374 that is now handled in a simpler way.
2378 Several new internal C macros have been added that take a string literal as
2379 arguments, alongside existing routines that take the equivalent value as two
2380 arguments, a character pointer and a length. The advantage of this is that
2381 the length of the string is calculated automatically, rather than having to
2382 be done manually. These routines are now used where appropriate across the
2387 The code in F<gv.c> that determines whether a variable has a special meaning
2388 to Perl has been simplified.
2392 The C<DEBUGGING>-mode output for regex compilation and execution has been
2397 Several macros and functions have been added to the public API for
2398 dealing with Unicode and UTF-8-encoded strings. See
2399 L<perlapi/Unicode Support>.
2403 Use C<my_strlcat()> in C<locale.c>. While C<strcat()> is safe in this context,
2404 some compilers were optimizing this to C<strcpy()> causing a porting test to
2405 fail that looks for unsafe code. Rather than fighting this, we just use
2406 C<my_strlcat()> instead.
2410 Three new ops, C<OP_ARGELEM>, C<OP_ARGDEFELEM> and C<OP_ARGCHECK> have
2411 been added. These are intended principally to implement the individual
2412 elements of a subroutine signature, plus any overall checking required.
2416 Perl no longer panics when switching into some locales on machines with
2417 buggy C<strxfrm()> implementations in their libc. [perl #121734]
2421 Perl is now built with the C<PERL_OP_PARENT> compiler define enabled by
2422 default. To disable it, use the C<PERL_NO_OP_PARENT> compiler define.
2423 This flag alters how the C<op_sibling> field is used in C<OP> structures,
2424 and has been available optionally since perl 5.22.0.
2426 See L<perl5220delta/"Internal Changes"> for more details of what this
2431 The meanings of some internal SV flags have been changed
2433 OPpRUNTIME, SVpbm_VALID, SVpbm_TAIL, SvTAIL_on, SvTAIL_off, SVrepl_EVAL,
2438 Change C<hv_fetch(…, "…", …, …)> to C<hv_fetchs(…, "…", …)>
2440 The dual-life dists all use Devel::PPPort, so they can use this function even
2441 though it was only added in 5.10.
2445 =head1 Selected Bug Fixes
2451 C< $-{$name} > would leak an C<AV> on each access if the regular
2452 expression had no named captures. The same applies to access to any
2453 hash tied with L<Tie::Hash::NamedCapture> and C<< all =E<gt> 1 >>. [perl
2458 Attempting to use the deprecated variable C<$#> as the object in an
2459 indirect object method call could cause a heap use after free or
2460 buffer overflow. [perl #129274]
2464 When checking for an indirect object method call in some rare cases
2465 the parser could reallocate the line buffer but then continue to use
2466 pointers to the old buffer. [perl #129190]
2470 Supplying a glob as the format argument to L<perlfunc/formline> would
2471 cause an assertion failure. [perl #130722]
2475 Code like C< $value1 =~ qr/.../ ~~ $value2 > would have the match
2476 converted into a qr// operator, leaving extra elements on the stack to
2477 confuse any surrounding expression. [perl #130705]
2481 Since 5.24.0 in some obscure cases, a regex which included code blocks
2482 from multiple sources (e.g. via embedded via qr// objects) could end up
2483 with the wrong current pad and crash or give weird results. [perl #129881]
2487 Occasionally C<local()>s in a code block within a patterns weren't being
2488 undone when the pattern matching backtracked over the code block.
2493 Using C<substr()> to modify a magic variable could access freed memory
2494 in some cases. [perl #129340]
2498 Perl 5.25.9 was fixed so that under C<use utf8>, the entire Perl program
2499 is checked that the UTF-8 is wellformed. It turns out that several edge
2500 cases were missed, and are now fixed. [perl #126310] was the original
2505 Under C<use utf8>, the entire Perl program is now checked that the UTF-8
2506 is wellformed. This resolves [perl #126310].
2510 The range operator C<..> on strings now handles its arguments correctly when in
2511 the scope of the L<< C<unicode_strings>|feature/"The 'unicode_strings' feature" >>
2512 feature. The previous behaviour was sufficiently unexpected that we believe no
2513 correct program could have made use of it.
2517 The S<split> operator did not ensure enough space was allocated for
2518 its return value in scalar context. It could then write a single
2519 pointer immediately beyond the end of the memory block allocated for
2520 the stack. [perl #130262]
2524 Using a large code point with the C<W> pack template character with
2525 the current output position aligned at just the right point could
2526 cause a write a single zero byte immediately beyond the end of an
2527 allocated buffer. [perl #129149]
2531 Supplying the form picture argument as part of the form argument list
2532 where the picture specifies modifying the argument could cause an
2533 access to the new freed compiled form. [perl #129125]
2537 Fix a problem with sort's build-in compare, where it would not sort
2538 correctly with 64-bit integers, and non-long doubles. [perl #130335]
2542 Fix issues with /(?{ ... E<lt>E<lt>EOF })/ that broke Method-Signatures. [perl #130398]
2546 Fix a macro which caused syntax error on an EBCDIC build.
2550 Prevent tests from getting hung up on 'NonStop' option. [perl #130445]
2554 Fixed an assertion failure with C<chop> and C<chomp>, which
2555 could be triggered by C<chop(@x =~ tr/1/1/)>. [perl #130198].
2559 Fixed a comment skipping error under C</x>; it could stop skipping a
2560 byte early, which could be in the middle of a UTF-8 character.
2565 F<perldb> now ignores F</dev/tty> on non-Unix systems. [perl #113960];
2569 Fix assertion failure for C<{}-E<gt>$x> when C<$x> isn't defined. [perl #130496].
2573 DragonFly BSD now has support for setproctitle(). [perl #130068].
2577 Fix an assertion error which could be triggered when lookahead string
2578 in patterns exceeded a minimum length. [perl #130522].
2582 Only warn once per literal about a misplaced C<_>. [perl #70878].
2586 Ensure range-start is set after error in C<tr///>. [perl #129342].
2590 Don't read past start of string for unmatched backref; otherwise,
2591 we may have heap buffer overflow. [perl #129377].
2595 Properly recognize mathematical digit ranges starting at U+1D7E.
2596 C<use re 'strict'> is supposed to warn if you use a range whose start
2597 and end digit aren't from the same group of 10. It didn't do that
2598 for five groups of mathematical digits starting at U+1D7E.
2602 A sub containing a "forward" declaration with the same name (e.g.,
2603 C<sub c { sub c; }>) could sometimes crash or loop infinitely. [perl
2608 A crash in executing a regex with a floating UTF-8 substring against a
2609 target string that also used UTF-8 has been fixed. [perl #129350]
2613 Previously, a shebang line like C<#!perl -i u> could be erroneously
2614 interpreted as requesting the C<-u> option. This has been fixed. [perl
2619 The regex engine was previously producing incorrect results in some rare
2620 situations when backtracking past a trie that matches only one thing; this
2621 showed up as capture buffers (C<$1>, C<$2>, etc) erroneously containing data
2622 from regex execution paths that weren't actually executed for the final
2623 match. [perl #129897]
2627 Certain regexes making use of the experimental C<regex_sets> feature could
2628 trigger an assertion failure. This has been fixed. [perl #129322]
2632 Invalid assignments to a reference constructor (e.g., C<\eval=time>) could
2633 sometimes crash in addition to giving a syntax error. [perl #125679]
2637 The parser could sometimes crash if a bareword came after C<evalbytes>.
2642 Autoloading via a method call would warn erroneously ("Use of inherited
2643 AUTOLOAD for non-method") if there was a stub present in the package into
2644 which the invocant had been blessed. The warning is no longer emitted in
2645 such circumstances. [perl #47047]
2649 A sub containing with a "forward" declaration with the same name (e.g.,
2650 C<sub c { sub c; }>) could sometimes crash or loop infinitely. [perl
2655 The use of C<splice> on arrays with nonexistent elements could cause other
2656 operators to crash. [perl #129164]
2660 Fixed case where C<re_untuit_start> will overshoot the length of a utf8
2661 string. [perl #129012]
2665 Handle C<CXt_SUBST> better in C<Perl_deb_stack_all>, previously it wasn't
2666 checking that the I<current> C<cx> is the right type, and instead was always
2667 checking the base C<cx> (effectively a noop). [perl #129029]
2671 Fixed two possible use-after-free bugs in C<Perl_yylex>. C<Perl_yylex>
2672 maintains up to two pointers into the parser buffer, one of which can
2673 become stale under the right conditions. [perl #129069]
2677 Fixed a crash with C<s///l> where it thought it was dealing with UTF-8
2678 when it wasn't. [perl #129038]
2682 Fixed place where regex was not setting the syntax error correctly.
2687 The C<&.> operator (and the C<&> operator, when it treats its arguments as
2688 strings) were failing to append a trailing null byte if at least one string
2689 was marked as utf8 internally. Many code paths (system calls, regexp
2690 compilation) still expect there to be a null byte in the string buffer
2691 just past the end of the logical string. An assertion failure was the
2692 result. [perl #129287]
2696 Check C<pack_sockaddr_un()>'s return value because C<pack_sockaddr_un()>
2697 silently truncates the supplied path if it won't fit into the C<sun_path>
2698 member of C<sockaddr_un>. This may change in the future, but for now
2699 check the path in theC<sockaddr> matches the desired path, and skip if
2700 it doesn't. [perl #128095]
2704 Make sure C<PL_oldoldbufptr> is preserved in C<scan_heredoc()>. In some
2705 cases this is used in building error messages. [perl #128988]
2709 Check for null PL_curcop in IN_LC() [perl #129106]
2713 Fixed the parser error handling for an 'C<:attr(foo>' that does not have
2718 Fix C<Perl_delimcpy()> to handle a backslash as last char, this
2719 actually fixed two bugs, [perl #129064] and [perl #129176].
2723 [perl #129267] rework gv_fetchmethod_pvn_flags separator parsing to
2724 prevent possible string overrun with invalid len in gv.c
2728 Problems with in-place array sorts: code like C<@a = sort { ... } @a>,
2729 where the source and destination of the sort are the same plain array, are
2730 optimised to do less copying around. Two side-effects of this optimisation
2731 were that the contents of C<@a> as visible to to sort routine were
2732 partially sorted, and under some circumstances accessing C<@a> during the
2733 sort could crash the interpreter. Both these issues have been fixed, and
2734 Sort functions see the original value of C<@a>.
2738 Non-ASCII string delimiters are now reported correctly in error messages
2739 for unterminated strings. [perl #128701]
2743 C<pack("p", ...)> used to emit its warning ("Attempt to pack pointer to
2744 temporary value") erroneously in some cases, but has been fixed.
2748 C<@DB::args> is now exempt from "used once" warnings. The warnings only
2749 occurred under B<-w>, because F<warnings.pm> itself uses C<@DB::args>
2754 The use of built-in arrays or hash slices in a double-quoted string no
2755 longer issues a warning ("Possible unintended interpolation...") if the
2756 variable has not been mentioned before. This affected code like
2757 C<qq|@DB::args|> and C<qq|@SIG{'CHLD', 'HUP'}|>. (The special variables
2758 C<@-> and C<@+> were already exempt from the warning.)
2762 C<gethostent> and similar functions now perform a null check internally, to
2763 avoid crashing with torsocks. This was a regression from 5.22. [perl
2768 C<defined *{'!'}>, C<defined *{'['}>, and C<defined *{'-'}> no longer leak
2769 memory if the typeglob in question has never been accessed before.
2773 Mentioning the same constant twice in a row (which is a syntax error) no
2774 longer fails an assertion under debugging builds. This was a regression
2775 from 5.20. [perl #126482]
2779 Many issues relating to C<printf "%a"> of hexadecimal floating point
2780 were fixed. In addition, the "subnormals" (formerly known as "denormals")
2781 floating point anumbers are now supported both with the plain IEEE 754
2782 floating point numbers (64-bit or 128-bit) and the x86 80-bit
2783 "extended precision". Note that subnormal hexadecimal floating
2784 point literals will give a warning about "exponent underflow".
2785 [perl #128843, #128889, #128890, #128893, #128909, #128919]
2789 A regression in 5.24 with C<tr/\N{U+...}/foo/> when the code point was between
2790 128 and 255 has been fixed. [perl #128734].
2794 A regression from the previous development release, 5.23.3, where
2795 compiling a regular expression could crash the interpreter has been
2796 fixed. [perl #128686].
2800 Use of a string delimiter whose code point is above 2**31 now works
2801 correctly on platforms that allow this. Previously, certain characters,
2802 due to truncation, would be confused with other delimiter characters
2803 with special meaning (such as C<?> in C<m?...?>), resulting
2804 in inconsistent behaviour. Note that this is non-portable,
2805 and is based on Perl's extension to UTF-8, and is probably not
2806 displayable nor enterable by any editor. [perl #128738]
2810 C<@{x> followed by a newline where C<x> represents a control or non-ASCII
2811 character no longer produces a garbled syntax error message or a crash.
2816 An assertion failure with C<%: = 0> has been fixed.
2817 L<[perl #128238]|https://rt.perl.org/Public/Bug/Display.html?id=128238>
2821 In Perl 5.18, the parsing of C<"$foo::$bar"> was accidentally changed, such
2822 that it would be treated as C<$foo."::".$bar>. The previous behavior, which
2823 was to parse it as C<$foo:: . $bar>, has been restored.
2824 L<[perl #128478]|https://rt.perl.org/Public/Bug/Display.html?id=128478>
2828 Since Perl 5.20, line numbers have been off by one when perl is invoked with
2829 the B<-x> switch. This has been fixed.
2830 L<[perl #128508]|https://rt.perl.org/Public/Bug/Display.html?id=128508>
2834 Vivifying a subroutine stub in a deleted stash (e.g., C<delete $My::{"Foo::"};
2835 \&My::Foo::foo>) no longer crashes. It had begun crashing in Perl 5.18.
2836 L<[perl #128532]|https://rt.perl.org/Public/Bug/Display.html?id=128532>
2840 Some obscure cases of subroutines and file handles being freed at the same time
2841 could result in crashes, but have been fixed. The crash was introduced in Perl
2843 L<[perl #128597]|https://rt.perl.org/Public/Bug/Display.html?id=128597>
2847 Code that looks for a variable name associated with an uninitialized value
2848 could cause an assertion in cases where magic is involved, such as
2849 C<$ISA[0][0]>. This has now been fixed.
2850 L<[perl #128253]|https://rt.perl.org/Public/Bug/Display.html?id=128253>
2854 A crash caused by code generating the warning "Subroutine STASH::NAME
2855 redefined" in cases such as C<sub P::f{} undef *P::; *P::f =sub{};> has been
2856 fixed. In these cases, where the STASH is missing, the warning will now appear
2857 as "Subroutine NAME redefined".
2858 L<[perl #128257]|https://rt.perl.org/Public/Bug/Display.html?id=128257>
2862 Fixed an assertion triggered by some code that handles deprecated behavior in
2863 formats, e.g. in cases like this:
2869 L<[perl #128255]|https://rt.perl.org/Public/Bug/Display.html?id=128255>
2873 A possible divide by zero in string transformation code on Windows has been
2874 avoided, fixing a crash when collating an empty string.
2875 L<[perl #128618]|https://rt.perl.org/Public/Bug/Display.html?id=128618>
2879 Some regular expression parsing glitches could lead to assertion failures with
2880 regular expressions such as C</(?E<lt>=/> and C</(?E<lt>!/>. This has now been fixed.
2881 L<[perl #128170]|https://rt.perl.org/Public/Bug/Display.html?id=128170>
2885 C< until ($x = 1) { ... } > and C< ... until $x = 1 > now properly
2886 warn when syntax warnings are enabled. [perl #127333]
2890 socket() now leaves the error code returned by the system in C<$!> on
2891 failure. [perl #128316]
2895 Assignment variants of any bitwise ops under the C<bitwise> feature would
2896 crash if the left-hand side was an array or hash. [perl #128204]
2900 C<require> followed by a single colon (as in C<foo() ? require : ...> is
2901 now parsed correctly as C<require> with implicit $_, rather than
2902 C<require "">. [perl #128307]
2906 Scalar C<keys %hash> can now be assigned to consistently in all scalar
2907 lvalue contexts. Previously it worked for some contexts but not others.
2911 List assignment to C<vec> or C<substr> with an array or hash for its first
2912 argument used to result in crashes or "Can't coerce" error messages at run
2913 time, unlike scalar assignment, which would give an error at compile time.
2914 List assignment now gives a compile-time error, too. [perl #128260]
2918 Expressions containing an C<&&> or C<||> operator (or their synonyms C<and>
2919 and C<or>) were being compiled incorrectly in some cases. If the left-hand
2920 side consisted of either a negated bareword constant or a negated C<do {}>
2921 block containing a constant expression, and the right-hand side consisted of
2922 a negated non-foldable expression, one of the negations was effectively
2923 ignored. The same was true of C<if> and C<unless> statement modifiers,
2924 though with the left-hand and right-hand sides swapped. This long-standing
2925 bug has now been fixed. [perl #127952]
2929 C<reset> with an argument no longer crashes when encountering stash entries
2930 other than globs. [perl #128106]
2934 Assignment of hashes to, and deletion of, typeglobs named C<*::::::> no
2935 longer causes crashes. [perl #128086]
2939 Handle SvIMMORTALs in LHS of list assign. [perl #129991]
2943 [perl #130010] a5540cf breaks texinfo
2945 This involved user-defined Unicode properties.
2949 Fix error message for unclosed C<\N{> in regcomp.
2951 An unclosed C<\N{> could give the wrong error message
2952 C<"\N{NAME} must be resolved by the lexer">.
2956 List assignment in list context where the LHS contained aggregates and
2957 where there were not enough RHS elements, used to skip scalar lvalues.
2958 Previously, C<(($a,$b,@c,$d) = (1))> in list context returned C<($a)>; now
2959 it returns C<($a,$b,$d)>. C<(($a,$b,$c) = (1))> is unchanged: it still
2960 returns C<($a,$b,$c)>. This can be seen in the following:
2962 sub inc { $_++ for @_ }
2963 inc(($a,$b,@c,$d) = (10))
2965 Formerly, the values of C<($a,$b,$d)> would be left as C<(11,undef,undef)>;
2966 now they are C<(11,1,1)>.
2972 The basic problem is that code like this: /(?{ s!!! })/ can trigger infinite
2973 recursion on the C stack (not the normal perl stack) when the last successful
2974 pattern in scope is itself. Since the C stack overflows this manifests as an
2975 untrappable error/segfault, which then kills perl.
2977 We avoid the segfault by simply forbidding the use of the empty pattern when it
2978 would resolve to the currently executing pattern.
2982 [perl 128997] Avoid reading beyond the end of the line buffer when there's a
2983 short UTF-8 character at the end.
2987 [perl 129950] fix firstchar bitmap under utf8 with prefix optimisation.
2991 [perl 129954] Carp/t/arg_string.t: be liberal in f/p formats.
2995 [perl 129928] make do "a\0b" fail silently instead of throwing.
2999 [perl 129130] make chdir allocate the stack it needs.
3003 =head1 Known Problems
3009 Some modules have been broken by the L<context stack rework|/Internal Changes>.
3010 These modules were relying on non-guaranteed implementation details in perl.
3011 Their maintainers have been informed, and should contact perl5-porters for
3012 advice if needed. Below is a subset of these modules:
3016 =item * L<Algorithm::Permute>
3020 L<Coro> and perl v5.22.0 were already incompatible due to a change in the perl,
3021 and the reworking on the perl context stack creates a further incompatibility.
3022 perl5-porters has L<discussed the issue on the mailing
3023 list|http://www.nntp.perl.org/group/perl.perl5.porters/2016/05/msg236174.html>.
3025 =item * L<Data::Alias>
3029 =item * L<Scope::Upper>
3037 The module L<lexical::underscore> no longer works on perl v5.24.0, because perl
3038 no longer has a lexical C<$_>!
3042 C<mod_perl> has been patched for compatibility for v5.22.0 and later but no
3043 release has been made. The relevant patch (and other changes) can be found in
3044 their source code repository, L<mirrored at
3045 GitHub|https://github.com/apache/mod_perl/commit/82827132efd3c2e25cc413c85af61bb63375da6e>.
3049 =head1 Errata From Previous Releases
3055 Parsing bad POSIX charclasses no longer leaks memory. This was fixed in Perl
3057 L<[perl #128313]|https://rt.perl.org/Public/Bug/Display.html?id=128313>
3061 Fixed issues with recursive regexes. The behavior was fixed in Perl 5.24.0.
3062 L<[perl #126182]|https://rt.perl.org/Public/Bug/Display.html?id=126182>
3068 Jon Portnoy (AVENJ), a prolific Perl author and admired Gentoo community
3069 member, has passed away on August 10, 2016. He will be remembered and
3070 missed by all those with which he came in contact and enriched with his
3071 intellect, wit, and spirit.
3073 It is with great sadness we also note Kip Hampton's passing.. Probably
3074 best known as the author of the Perl & XML column on XML.com, he was a
3075 core contributor to AxKit, an XML server platform that became an Apache
3076 Foundation project. He was a frequent speaker in the early days at
3077 OSCON, and most recently at YAPC::NA in Madison. He was frequently on
3078 irc.perl.org as `ubu`, generally in the #axkit-dahut community, the
3079 group responsible for YAPC::NA Asheville in 2011.
3081 Kip and his constant contributions to the community will be greatly
3084 =head1 Acknowledgements
3086 Perl 5.26.0 represents approximately 12 months of development since Perl 5.24.0
3087 and contains approximately 370,000 lines of changes across 2,600 files from 86
3090 Excluding auto-generated files, documentation and release tools, there were
3091 approximately 230,000 lines of changes to 1,800 .pm, .t, .c and .h files.
3093 Perl continues to flourish into its third decade thanks to a vibrant community
3094 of users and developers. The following people are known to have contributed the
3095 improvements that became Perl 5.24.1:
3097 Aaron Crane, Abigail, Ævar Arnfjörð Bjarmason, Alex Vandiver, Andreas
3098 König, Andreas Voegele, Andrew Fresh, Andy Lester, Aristotle Pagaltzis, Chad
3099 Granum, Chase Whitener, Chris 'BinGOs' Williams, Chris Lamb, Christian Hansen,
3100 Christian Millour, Colin Newell, Craig A. Berry, Dagfinn Ilmari Mannsåker, Dan
3101 Collins, Daniel Dragan, Dave Cross, Dave Rolsky, David Golden, David H.
3102 Gutteridge, David Mitchell, Dominic Hargreaves, Doug Bell, E. Choroba, Ed Avis,
3103 Father Chrysostomos, François Perrad, Hauke D, H.Merijn Brand, Hugo van der
3104 Sanden, Ivan Pozdeev, James E Keenan, James Raspass, Jarkko Hietaniemi, Jerry
3105 D. Hedden, Jim Cromie, J. Nick Koston, John Lightsey, Karen Etheridge, Karl
3106 Williamson, Leon Timmermans, Lukas Mai, Matthew Horsfall, Maxwell Carey, Misty
3107 De Meo, Neil Bowers, Nicholas Clark, Nicolas R., Niko Tyni, Pali, Paul
3108 Marquess, Peter Avalos, Petr Písař, Pino Toscano, Rafael Garcia-Suarez, Reini
3109 Urban, Renee Baecker, Ricardo Signes, Richard Levitte, Rick Delaney, Salvador
3110 Fandiño, Samuel Thibault, Sawyer X, Sébastien Aperghis-Tramoni, Sergey
3111 Aleynikov, Shlomi Fish, Smylers, Stefan Seifert, Steffen Müller, Stevan
3112 Little, Steve Hay, Steven Humphrey, Sullivan Beck, Theo Buehler, Thomas Sibley,
3113 Todd Rinaldo, Tomasz Konojacki, Tony Cook, Unicode Consortium, Yaroslav Kuzmin,
3116 The list above is almost certainly incomplete as it is automatically generated
3117 from version control history. In particular, it does not include the names of
3118 the (very much appreciated) contributors who reported issues to the Perl bug
3121 Many of the changes included in this version originated in the CPAN modules
3122 included in Perl's core. We're grateful to the entire CPAN community for
3123 helping Perl to flourish.
3125 For a more complete list of all of Perl's historical contributors, please see
3126 the F<AUTHORS> file in the Perl source distribution.
3128 =head1 Reporting Bugs
3130 If you find what you think is a bug, you might check the articles recently
3131 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
3132 L<https://rt.perl.org/> . There may also be information at
3133 L<http://www.perl.org/> , the Perl Home Page.
3135 If you believe you have an unreported bug, please run the L<perlbug> program
3136 included with your release. Be sure to trim your bug down to a tiny but
3137 sufficient test case. Your bug report, along with the output of C<perl -V>,
3138 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
3140 If the bug you are reporting has security implications which make it
3141 inappropriate to send to a publicly archived mailing list, then see
3142 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
3143 for details of how to report the issue.
3147 The F<Changes> file for an explanation of how to view exhaustive details on
3150 The F<INSTALL> file for how to build Perl.
3152 The F<README> file for general stuff.
3154 The F<Artistic> and F<Copying> files for copyright information.