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.
105 =head2 create a safer utf8_hop() called utf8_hop_safe()
107 Unlike utf8_hop(), utf8_hop_safe() won't navigate before the beginning or after
108 the end of the supplied buffer.
110 =head2 @{^CAPTURE}, %{^CAPTURE}, and %{^CAPTURE_ALL}
112 C<@{^CAPTURE}> exposes the capture buffers of the last match as an
113 array. So C<$1> is C<${^CAPTURE}[0]>. This is a more efficient equivalent
114 to code like C<substr($matched_string,$-[0],$+[0]-$-[0])>, and you don't
115 have to keep track of the C<$matched_string> either. This variable has no
116 single character equivalent. Note like the other regex magic variables
117 the contents of this variable is dynamic, if you wish to store it beyond
118 the lifetime of the match you must copy it to another array.
120 C<%{^CAPTURE}> is the equivalent to C<%+> (ie named captures). Other than
121 being more self documenting there is no difference between the two forms.
123 C<%{^CAPTURE_ALL}> is the equivalent to C<%-> (ie all named captures).
124 Other than being more self documenting there is no difference between the
127 =head2 Unicode 9.0 is now supported
129 A list of changes is at L<http://www.unicode.org/versions/Unicode9.0.0/>.
130 Modules that are shipped with core Perl but not maintained by p5p do not
131 necessarily support Unicode 9.0. L<Unicode::Normalize> does work on 9.0.
133 =head2 Use of C<\p{I<script>}> uses the improved Script_Extensions property
135 Unicode 6.0 introduced an improved form of the Script (C<sc>) property, and
136 called it Script_Extensions (C<scx>). As of now, Perl uses this improved
137 version when a property is specified as just C<\p{I<script>}>. The meaning of
138 compound forms, like C<\p{sc=I<script>}> are unchanged. This should make
139 programs be more accurate when determining if a character is used in a given
140 script, but there is a slight chance of breakage for programs that very
141 specifically needed the old behavior. See L<perlunicode/Scripts>.
143 =head2 Declaring a reference to a variable
145 As an experimental feature, Perl now allows the referencing operator to come
146 after L<C<my()>|perlfunc/my>, L<C<state()>|perlfunc/state>,
147 L<C<our()>|perlfunc/our>, or L<C<local()>|perlfunc/local>. This syntax must
148 be enabled with C<use feature 'declared_refs'>. It is experimental, and will
149 warn by default unless C<no warnings 'experimental::refaliasing'> is in effect.
150 It is intended mainly for use in assignments to references. For example:
152 use experimental 'refaliasing', 'declared_refs';
155 See L<perlref/Assigning to References> for more details.
157 =head2 Perl can now do default collation in UTF-8 locales on platforms
160 Some platforms natively do a reasonable job of collating and sorting in
161 UTF-8 locales. Perl now works with those. For portability and full
162 control, L<Unicode::Collate> is still recommended, but now you may
163 not need to do anything special to get good-enough results, depending on
164 your application. See
165 L<perllocale/Category C<LC_COLLATE>: Collation: Text Comparisons and Sorting>.
167 =head2 Better locale collation of strings containing embedded C<NUL>
170 In locales that have multi-level character weights, these are now
171 ignored at the higher priority ones. There are still some gotchas in
172 some strings, though. See
173 L<perllocale/Collation of strings containing embedded C<NUL> characters>.
175 =head2 Lexical subroutines are no longer experimental
177 Using the C<lexical_subs> feature introduced in v5.18 no longer emits a warning. Existing
178 code that disables the C<experimental::lexical_subs> warning category
179 that the feature previously used will continue to work. The
180 C<lexical_subs> feature has no effect; all Perl code can use lexical
181 subroutines, regardless of what feature declarations are in scope.
183 =head2 C<CORE> subroutines for hash and array functions callable via
186 The hash and array functions in the C<CORE> namespace--C<keys>, C<each>,
187 C<values>, C<push>, C<pop>, C<shift>, C<unshift> and C<splice>--, can now
188 be called with ampersand syntax (C<&CORE::keys(\%hash>) and via reference
189 (C<< my $k = \&CORE::keys; $k-E<gt>(\%hash) >>). Previously they could only be
192 =head2 POSIX::tmpnam() has been removed
194 The fundamentally unsafe C<tmpnam()> interface was deprecated in
195 Perl 5.22.0 and has now been removed. In its place you can use
196 for example the L<File::Temp> interfaces.
198 =head2 require ::Foo::Bar is now illegal.
200 Formerly, C<require ::Foo::Bar> would try to read F</Foo/Bar.pm>. Now any
201 bareword require which starts with a double colon dies instead.
203 =head2 Unescaped literal C<"{"> characters in regular expression
204 patterns are no longer permissible
206 You have to now say something like C<"\{"> or C<"[{]"> to specify to
207 match a LEFT CURLY BRACKET. This will allow future extensions to the
208 language. This restriction is not enforced, nor are there current plans
209 to enforce it, if the C<"{"> is the first character in the pattern.
211 These have been deprecated since v5.16, with a deprecation message
212 displayed starting in v5.22.
214 =head2 Literal control character variable names are no longer permissible
216 A variable name may no longer contain a literal control character under
217 any circumstances. These previously were allowed in single-character
218 names on ASCII platforms, but have been deprecated there since Perl
219 v5.20. This affects things like C<$I<\cT>>, where I<\cT> is a literal
220 control (such as a C<NAK> or C<NEGATIVE ACKNOWLEDGE> character) in the
223 =head2 C<NBSP> is no longer permissible in C<\N{...}>
225 The name of a character may no longer contain non-breaking spaces. It
226 has been deprecated to do so since Perl v5.22.
228 =head2 create a safer utf8_hop() called utf8_hop_safe()
230 Unlike utf8_hop(), utf8_hop_safe() won't navigate before the beginning or after
231 the end of the supplied buffer.
235 =head2 Removal of the current directory (C<.>) from C<@INC>
237 The perl binary includes a default set of paths in C<@INC>. Historically
238 it has also included the current directory (C<.>) as the final entry,
239 unless run with taint mode enabled (C<perl -T>). While convenient, this has
240 security implications: for example, where a script attempts to load an
241 optional module when its current directory is untrusted (such as F</tmp>),
242 it could load and execute code from under that directory.
244 Starting with v5.26.0, C<.> is always removed by default, not just under
245 tainting. This has major implications for installing modules and executing
248 The following new features have been added to help ameliorate these
253 =item * C<Configure -Udefault_inc_excludes_dot>
255 There is a new C<Configure> option, C<default_inc_excludes_dot> (enabled
256 by default) which builds a perl executable without C<.>; unsetting this
257 option using C<-U> reverts perl to the old behaviour. This may fix your
258 path issues but will reintroduce all the security concerns, so don't
259 build a perl executable like this unless you're I<really> confident that
260 such issues are not a concern in your environment.
262 =item * C<$PERL_USE_UNSAFE_INC>
264 There is a new environment variable recognised by the perl interpreter.
265 If this variable has the value C<1> when the perl interpreter starts up,
266 then C<.> will be automatically appended to C<@INC> (except under tainting).
268 This allows you restore the old perl interpreter behaviour on a
269 case-by-case basis. But note that this intended to be a temporary crutch,
270 and this feature will likely be removed in some future perl version.
271 It is currently set by the C<cpan> utility and C<Test::Harness> to
272 ease installation of CPAN modules which have not been updated handle the
273 lack of dot. Once again, don't use this unless you are sure that this
274 will not reintroduce any security concerns.
276 =item * A new mandatory warning issued by C<do>.
278 While it is well-known that C<use> and C<require> use C<@INC> to search
279 for the file to load, many people don't realise that C<do "file"> also
280 searches C<@INC> if the file is a relative path. With the removal of C<.>,
281 a simple C<do "file.pl"> will fail to read in and execute C<file.pl> from
282 the current directory. Since this is commonly expected behaviour, a new
283 mandatory warning is now issued whenever C<do> fails to load a file which
284 it otherwise would have found if dot had been in C<@INC>.
288 Here are some things script and module authors may need to do to make
289 their software work in the new regime.
293 =item * Script authors
295 If the issue is within your own code (rather than within included
296 modules), then you have two main options. Firstly, if you are confident
297 that your script will only be run within a trusted directory (under which
298 you expect to find trusted files and modules), then add C<.> back into the
302 my $dir = "/some/trusted/directory";
303 chdir $dir or die "Can't chdir to $dir: $!\n";
307 use "Foo::Bar"; # may load /some/trusted/directory/Foo/Bar.pm
308 do "config.pl"; # may load /some/trusted/directory/config.pl
310 On the other hand, if your script is intended to be run from within
311 untrusted directories (such as F</tmp>), then your script suddenly failing
312 to load files may be indicative of a security issue. You most likely want
313 to replace any relative paths with full paths; for example,
319 do "$ENV{HOME}/.foo_config.pl"
321 If you are absolutely certain that you want your script to load and
322 execute a file from the current directory, then use a C<./> prefix; for
325 do "./.foo_config.pl"
327 =item * Installing and using CPAN modules
329 If you install a CPAN module using an automatic tool like C<cpan>, then
330 this tool will itself set the C<PERL_USE_UNSAFE_INC> environment variable
331 while building and testing the module, which may be sufficient to install
332 a distribution which hasn't been updated to be dot-aware. If you want to
333 install such a module manually, then you'll need to replace the
334 traditional invocation:
336 perl Makefile.PL && make && make test && make install
340 (export PERL_USE_UNSAFE_INC=1; \
341 perl Makefile.PL && make && make test && make install)
343 Note that this only helps build and install an unfixed module. It's
344 possible for the tests to pass (since they were run under
345 C<PERL_USE_UNSAFE_INC=1>), but for the module itself to fail to perform
346 correctly in production. In this case you may have to temporarily modify
347 your script until such time as fixed version of the module is released.
352 local @INC = (@INC, '.');
353 # assuming read_config() needs '.' in @INC
354 $config = Foo::Bar->read_config();
357 This is only rarely expected to be necessary. Again, if doing this,
358 assess the resultant risks first.
360 =item * Module Authors
362 If you maintain a CPAN distribution, it may need updating to run in
363 a dotless environment. Although C<cpan> and other such tools will
364 currently set the C<PERL_USE_UNSAFE_INC> during module build, this is
365 temporary workaround for the set of modules which rely on C<.> being in
366 C<@INC> for installation and testing, and this may mask deeper issues. It
367 could result in a module which passes tests and installs, but which
370 During build, test and install, it will normally be the case that any perl
371 processes will be executing directly within the root directory of the
372 untarred distribution, or a known subdirectory of that, such as F<t/>. It
373 may well be that F<Makefile.PL> or F<t/foo.t> will attempt to include
374 local modules and configuration files using their direct relative
375 filenames, which will now fail.
377 However, as described above, automatic tools like F<cpan> will (for now)
378 set the C<PERL_USE_UNSAFE_INC> environment variable, which introduces
381 This makes it likely that your existing build and test code will work, but
382 this may mask issues with your code which only manifest when used after
383 install. It is prudent to try and run your build process with that
384 variable explicitly disabled:
385 (export PERL_USE_UNSAFE_INC=0; \
386 perl Makefile.PL && make && make test && make install)
388 This is more likely to show up any potential problems with your module's
389 build process, or even with the module itself. Fixing such issues will
390 ensure both that your module can again be installed manually, and that
391 it will still build once the C<PERL_USE_UNSAFE_INC> crutch goes away.
393 When fixing issues in tests due to the removal of dot from C<@INC>,
394 reinsertion of dot into C<@INC> should be performed with caution, for this
395 too may suppress real errors in your runtime code. You are encouraged
396 wherever possible to apply the aforementioned approaches with explicit
397 absolute/relative paths, or relocate your needed files into a subdirectory
398 and insert that subdirectory into C<@INC> instead.
400 If your runtime code has problems under the dotless C<@INC>, then the comments
401 above on how to fix for script authors will mostly apply here too. Bear in
402 mind though that it is considered bad form for a module to globally add dot to
403 C<@INC>, since it introduces both a security risk and hides issues of
404 accidentally requiring dot in C<@INC>, as explained above.
408 =head2 "Escaped" colons and relative paths in PATH
410 On Unix systems, Perl treats any relative paths in the PATH environment
411 variable as tainted when starting a new process. Previously, it was
412 allowing a backslash to escape a colon (unlike the OS), consequently
413 allowing relative paths to be considered safe if the PATH was set to
414 something like C</\:.>. The check has been fixed to treat C<.> as tainted
417 =head2 C<-Di> switch is now required for PerlIO debugging output
419 Previously PerlIO debugging output would be sent to the file specified
420 by the C<PERLIO_DEBUG> environment variable if perl wasn't running
421 setuid and the C<-T> or C<-t> switches hadn't been parsed yet.
423 If perl performed output at a point where it hadn't yet parsed its
424 switches this could result in perl creating or overwriting the file
425 named by C<PERLIO_DEBUG> even when the C<-T> switch had been supplied.
427 Perl now requires the C<-Di> switch to produce PerlIO debugging
428 output. By default this is written to C<stderr>, but can optionally
429 be redirected to a file by setting the C<PERLIO_DEBUG> environment
432 If perl is running setuid or the C<-T> switch has supplied
433 C<PERLIO_DEBUG> is ignored and the debugging output is sent to
434 C<stderr> as for any other C<-D> switch.
436 =head1 Incompatible Changes
438 =head2 C<${^ENCODING}> has been removed
440 Consequently, the L<encoding> pragma's default mode is no longer supported. If
441 you still need to write your source code in encodings other than UTF-8, use a
442 source filter such as L<Filter::Encoding> on CPAN or L<encoding>'s C<Filter>
445 =head2 C<scalar(%hash)> return signature changed
447 The value returned for C<scalar(%hash)> will no longer show information about
448 the buckets allocated in the hash. It will simply return the count of used
449 keys. It is thus equivalent to C<0+keys(%hash)>.
451 A form of backwards compatibility is provided via C<Hash::Util::bucket_ratio()>
452 which provides the same behavior as C<scalar(%hash)> provided prior to Perl
455 =head2 C<keys> returned from an lvalue subroutine
457 C<keys> returned from an lvalue subroutine can no longer be assigned
460 sub foo : lvalue { keys(%INC) }
462 sub bar : lvalue { keys(@_) }
463 (bar) = 3; # also an error
465 This makes the lvalue sub case consistent with C<(keys %hash) = ...> and
466 C<(keys @_) = ...>, which are also errors. [perl #128187]
470 =head2 String delimiters that aren't stand-alone graphemes are now deprecated
472 In order for Perl to eventually allow string delimiters to be Unicode
473 grapheme clusters (which look like a single character, but may be
474 a sequence of several ones), we have to stop allowing a single char
475 delimiter that isn't a grapheme by itself. These are unlikely to exist
476 in actual code, as they would typically display as attached to the
477 character in front of them.
479 =head1 Performance Enhancements
485 A hash in boolean context is now sometimes faster, e.g.
489 This was already special-cased, but some cases were missed, and even the
490 ones which weren't have been improved.
494 Several other ops may now also be faster in boolean context.
496 =item * New Faster Hash Function on 64 bit builds
498 We use a different hash function for short and long keys. This should
499 improve performance and security, especially for long keys.
501 =item * readline is faster
503 Reading from a file line-by-line with C<readline()> or C<< E<lt>E<gt> >> should
504 now typically be faster due to a better implementation of the code that
505 searches for the next newline character.
509 Reduce cost of SvVALID().
513 C<$ref1 = $ref2> has been optimized.
517 Array and hash assignment are now faster, e.g.
522 especially when the RHS is empty.
526 Reduce the number of odd special cases for the C<SvSCREAM> flag.
530 Avoid sv_catpvn() in do_vop() when unneeded.
534 Enhancements in Regex concat COW implementation.
538 Clearing hashes and arrays has been made slightly faster. Now code
539 like this is around 5% faster:
542 for my $i (1..3_000_000) {
547 and this code around 3% faster:
550 for my $i (1..3_000_000) {
557 Better optimise array and hash assignment
561 Converting a single-digit string to a number is now substantially faster.
565 The internal op implementing the C<split> builtin has been simplified and
566 sped up. Firstly, it no longer requires a subsidiary internal C<pushre> op
567 to do its work. Secondly, code of the form C<my @x = split(...)> is now
568 optimised in the same way as C<@x = split(...)>, and is therefore a few
573 The rather slow implementation for the experimental subroutine signatures
574 feature has been made much faster; it is now comparable in speed with the
575 old-style C<my ($a, $b, @c) = @_>.
579 Bareword constant strings are now permitted to take part in constant
580 folding. They were originally exempted from constant folding in August 1999,
581 during the development of Perl 5.6, to ensure that C<use strict "subs">
582 would still apply to bareword constants. That has now been accomplished a
583 different way, so barewords, like other constants, now gain the performance
584 benefits of constant folding.
586 This also means that void-context warnings on constant expressions of
587 barewords now report the folded constant operand, rather than the operation;
588 this matches the behaviour for non-bareword constants.
592 =head1 Modules and Pragmata
594 =head2 Updated Modules and Pragmata
600 L<Archive::Tar> has been upgraded from version 2.04 to 2.24.
604 L<arybase> has been upgraded from version 0.11 to 0.12.
608 L<attributes> has been upgraded from version 0.27 to 0.29.
610 The deprecation message for the C<:unique> and C<:locked> attributes
611 now mention they will disappear in Perl 5.28.
615 L<B> has been upgraded from version 1.62 to 1.68.
619 L<B::Concise> has been upgraded from version 0.996 to 0.999.
621 Its output is now more descriptive for C<op_private> flags.
625 L<B::Debug> has been upgraded from version 1.23 to 1.24.
629 L<B::Deparse> has been upgraded from version 1.37 to 1.40.
633 L<B::Xref> has been upgraded from version 1.05 to 1.06.
635 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
639 L<base> has been upgraded from version 2.23 to 2.25.
643 L<bignum> has been upgraded from version 0.42 to 0.47.
647 L<Carp> has been upgraded from version 1.40 to 1.42.
651 L<charnames> has been upgraded from version 1.43 to 1.44.
655 L<Compress::Raw::Bzip2> has been upgraded from version 2.069 to 2.074.
659 L<Compress::Raw::Zlib> has been upgraded from version 2.069 to 2.074.
663 L<Config::Perl::V> has been upgraded from version 0.25 to 0.28.
667 L<CPAN> has been upgraded from version 2.11 to 2.18.
671 L<CPAN::Meta> has been upgraded from version 2.150005 to 2.150010.
675 L<Data::Dumper> has been upgraded from version 2.160 to 2.167.
677 The XS implementation now supports Deparse.
679 This fixes a stack management bug. [perl #130487].
683 L<DB_File> has been upgraded from version 1.835 to 1.840.
687 L<Devel::Peek> has been upgraded from version 1.23 to 1.26.
691 L<Devel::PPPort> has been upgraded from version 3.32 to 3.35.
695 L<Devel::SelfStubber> has been upgraded from version 1.05 to 1.06.
697 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
701 L<diagnostics> has been upgraded from version 1.34 to 1.36.
703 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
707 L<Digest> has been upgraded from version 1.17 to 1.17_01.
711 L<Digest::MD5> has been upgraded from version 2.54 to 2.55.
715 L<Digest::SHA> has been upgraded from version 5.95 to 5.96.
719 L<DynaLoader> has been upgraded from version 1.38 to 1.42.
723 L<Encode> has been upgraded from version 2.80 to 2.88.
727 L<encoding> has been upgraded from version 2.17 to 2.19.
729 This module's default mode is no longer supported as of Perl 5.25.3. It now
730 dies when imported, unless the C<Filter> option is being used.
734 L<encoding::warnings> has been upgraded from version 0.12 to 0.13.
736 This module is no longer supported as of Perl 5.25.3. It emits a warning to
737 that effect and then does nothing.
741 L<Errno> has been upgraded from version 1.25 to 1.28.
743 Document that using C<%!> loads Errno for you.
745 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
749 L<ExtUtils::Embed> has been upgraded from version 1.33 to 1.34.
751 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
755 L<ExtUtils::MakeMaker> has been upgraded from version 7.10_01 to 7.24.
759 L<ExtUtils::Miniperl> has been upgraded from version 1.05 to 1.06.
763 L<ExtUtils::ParseXS> has been upgraded from version 3.31 to 3.34.
767 L<ExtUtils::Typemaps> has been upgraded from version 3.31 to 3.34.
771 L<feature> has been upgraded from version 1.42 to 1.47.
773 Fixes the Unicode Bug in the range operator.
777 L<File::Copy> has been upgraded from version 2.31 to 2.32.
781 L<File::Fetch> has been upgraded from version 0.48 to 0.52.
785 L<File::Glob> has been upgraded from version 1.26 to 1.28.
787 Issue a deprecation message for C<File::Glob::glob()>.
791 L<File::Spec> has been upgraded from version 3.63 to 3.67.
795 L<FileHandle> has been upgraded from version 2.02 to 2.03.
799 L<Filter::Simple> has been upgraded from version 0.92 to 0.93.
801 It no longer treats C<no MyFilter> immediately following C<use MyFilter> as
802 end-of-file. [perl #107726]
806 L<Getopt::Long> has been upgraded from version 2.48 to 2.49.
810 L<Getopt::Std> has been upgraded from version 1.11 to 1.12.
814 L<Hash::Util> has been upgraded from version 0.19 to 0.22.
818 L<HTTP::Tiny> has been upgraded from version 0.056 to 0.070.
820 Internal 599-series errors now include the redirect history.
824 L<I18N::LangTags> has been upgraded from version 0.40 to 0.42.
826 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
830 L<IO> has been upgraded from version 1.36 to 1.38.
834 IO-Compress has been upgraded from version 2.069 to 2.074.
838 L<IO::Socket::IP> has been upgraded from version 0.37 to 0.38.
842 L<IPC::Cmd> has been upgraded from version 0.92 to 0.96.
846 L<IPC::SysV> has been upgraded from version 2.06_01 to 2.07.
850 L<JSON::PP> has been upgraded from version 2.27300 to 2.27400_02.
854 L<lib> has been upgraded from version 0.63 to 0.64.
856 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
860 L<List::Util> has been upgraded from version 1.42_02 to 1.46_02.
864 L<Locale::Codes> has been upgraded from version 3.37 to 3.42.
868 L<Locale::Maketext> has been upgraded from version 1.26 to 1.28.
872 L<Locale::Maketext::Simple> has been upgraded from version 0.21 to 0.21_01.
876 L<Math::BigInt> has been upgraded from version 1.999715 to 1.999806.
878 There have also been some core customizations.
882 L<Math::BigInt::FastCalc> has been upgraded from version 0.40 to 0.5005.
886 L<Math::BigRat> has been upgraded from version 0.260802 to 0.2611.
890 L<Math::Complex> has been upgraded from version 1.59 to 1.5901.
894 L<Memoize> has been upgraded from version 1.03 to 1.03_01.
898 L<Module::CoreList> has been upgraded from version 5.20170420 to 5.20170520.
902 L<Module::Load::Conditional> has been upgraded from version 0.64 to 0.68.
906 L<Module::Metadata> has been upgraded from version 1.000031 to 1.000033.
910 L<mro> has been upgraded from version 1.18 to 1.20.
914 L<Net::Ping> has been upgraded from version 2.43 to 2.55.
916 IPv6 addresses and C<AF_INET6> sockets are now supported, along with several
919 Remove sudo from 500_ping_icmp.t.
921 Avoid stderr noise in tests
923 Check for echo in new Net::Ping tests.
927 L<NEXT> has been upgraded from version 0.65 to 0.67.
931 L<Opcode> has been upgraded from version 1.34 to 1.39.
935 L<open> has been upgraded from version 1.10 to 1.11.
939 L<OS2::Process> has been upgraded from version 1.11 to 1.12.
941 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
945 L<overload> has been upgraded from version 1.26 to 1.28.
947 Its compilation speed has been improved slightly.
951 L<parent> has been upgraded from version 0.234 to 0.236.
955 L<perl5db.pl> has been upgraded from version 1.50 to 1.51.
957 Ignore F</dev/tty> on non-Unix systems. [perl #113960]
961 L<Perl::OSType> has been upgraded from version 1.009 to 1.010.
965 L<perlfaq> has been upgraded from version 5.021010 to 5.021011.
969 L<PerlIO> has been upgraded from version 1.09 to 1.10.
973 L<PerlIO::encoding> has been upgraded from version 0.24 to 0.25.
977 L<PerlIO::scalar> has been upgraded from version 0.24 to 0.26.
981 L<Pod::Checker> has been upgraded from version 1.60 to 1.73.
985 L<Pod::Functions> has been upgraded from version 1.10 to 1.11.
989 L<Pod::Html> has been upgraded from version 1.22 to 1.2202.
993 L<Pod::Perldoc> has been upgraded from version 3.25_02 to 3.28.
997 L<Pod::Simple> has been upgraded from version 3.32 to 3.35.
1001 L<Pod::Usage> has been upgraded from version 1.68 to 1.69.
1005 L<POSIX> has been upgraded from version 1.65 to 1.76. This remedies several
1006 defects in making its symbols exportable. [perl #127821]
1007 The C<POSIX::tmpnam()> interface has been removed,
1008 see L</"POSIX::tmpnam() has been removed">.
1009 Trying to import POSIX subs that have no real implementations
1010 (like C<POSIX::atend()>) now fails at import time, instead of
1011 waiting until runtime.
1015 L<re> has been upgraded from version 0.32 to 0.34
1017 This adds support for the new L<C<E<47>xx>|perlre/E<sol>x and E<sol>xx>
1018 regular expression pattern modifier, and a change to the L<S<C<use re
1019 'strict'>>|re/'strict' mode> experimental feature. When S<C<re
1020 'strict'>> is enabled, a warning now will be generated for all
1021 unescaped uses of the two characters C<}> and C<]> in regular
1022 expression patterns (outside bracketed character classes) that are taken
1023 literally. This brings them more in line with the C<)> character which
1024 is always a metacharacter unless escaped. Being a metacharacter only
1025 sometimes, depending on action at a distance, can lead to silently
1026 having the pattern mean something quite different than was intended,
1027 which the S<C<re 'strict'>> mode is intended to minimize.
1031 L<Safe> has been upgraded from version 2.39 to 2.40.
1035 L<Scalar::Util> has been upgraded from version 1.42_02 to 1.46_02.
1039 L<Storable> has been upgraded from version 2.56 to 2.62.
1041 Fixes [perl #130098].
1045 L<Symbol> has been upgraded from version 1.07 to 1.08.
1049 L<Sys::Syslog> has been upgraded from version 0.33 to 0.35.
1053 L<Term::ANSIColor> has been upgraded from version 4.04 to 4.06.
1057 L<Term::ReadLine> has been upgraded from version 1.15 to 1.16.
1059 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1063 L<Test> has been upgraded from version 1.28 to 1.30.
1065 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1069 L<Test::Harness> has been upgraded from version 3.36 to 3.38.
1073 L<Test::Simple> has been upgraded from version 1.001014 to 1.302073.
1077 L<Thread::Queue> has been upgraded from version 3.09 to 3.12.
1081 L<Thread::Semaphore> has been upgraded from 2.12 to 2.13.
1083 Added the C<down_timed> method.
1087 L<threads> has been upgraded from version 2.07 to 2.15.
1089 Compatibility with 5.8 has been restored.
1091 Fixes [perl #130469].
1095 L<threads::shared> has been upgraded from version 1.51 to 1.56.
1097 This fixes [cpan #119529], [perl #130457]
1101 L<Tie::Hash::NamedCapture> has been upgraded from version 0.09 to 0.10.
1105 L<Time::HiRes> has been upgraded from version 1.9733 to 1.9741.
1107 It now builds on systems with C++11 compilers (such as G++ 6 and Clang++
1110 Now uses C<clockid_t>.
1114 L<Time::Local> has been upgraded from version 1.2300 to 1.25.
1118 L<Unicode::Collate> has been upgraded from version 1.14 to 1.19.
1122 L<Unicode::UCD> has been upgraded from version 0.64 to 0.68.
1124 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1128 L<version> has been upgraded from version 0.9916 to 0.9917.
1132 L<VMS::DCLsym> has been upgraded from version 1.06 to 1.08.
1134 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1138 L<warnings> has been upgraded from version 1.36 to 1.37.
1142 L<XS::Typemap> has been upgraded from version 0.14 to 0.15.
1146 L<XSLoader> has been upgraded from version 0.21 to 0.27.
1148 Fixed a security hole in which binary files could be loaded from a path
1149 outside of L<C<@INC>|perlvar/@INC>.
1151 It now uses 3-arg C<open()> instead of 2-arg C<open()>. [perl #130122]
1155 =head1 Documentation
1157 =head2 New Documentation
1159 =head3 L<perldeprecation>
1161 This file documents all upcoming deprecations, and some of the deprecations
1162 which already have been removed. The purpose of this documentation is
1163 two-fold: document what will disappear, and by which version, and serve
1164 as a guide for people dealing with code which has features that no longer
1165 work after an upgrade of their perl.
1167 =head2 Changes to Existing Documentation
1175 Use of unassigned code point or non-standalone grapheme for a delimiter will be a fatal error starting in Perl 5.30
1177 This was changed to drop a leading C<v> in C<v5.30>, so it uses the same
1178 style as other deprecation messages.
1182 "\c%c" is more clearly written simply as "%s".
1184 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>
1188 Removed redundant C<dSP> from an example.
1192 =head3 L<perlcommunity>
1198 All references to Usenet have been removed.
1208 Updated documentation of C<scalar(%hash)>. See L</scalar(%hash) return
1209 signature changed> above.
1213 Use of single character variables, with the variable name a non printable
1214 character in the range C<\x80>-C<\xFF> is no longer allowed. Update the docs to
1225 All references to Usenet have been removed.
1235 Deprecations are to be marked with a D.
1236 C<"%s() is deprecated on :utf8 handles"> use a deprecation message, and as
1237 such, such be marked C<"(D deprecated)"> and not C<"(W deprecated)">.
1241 =head3 L<perlexperiment>
1247 Documented new feature: See L</Declaring a reference to a variable> above.
1257 Defined on aggregates is no longer allowed. Perlfunc was still reporting it as
1258 deprecated, and that it will be deleted in the future.
1262 Clarified documentation of L<C<seek()>|perlfunc/seek>,
1263 L<C<tell()>|perlfunc/tell> and L<C<sysseek()>|perlfunc/sysseek>.
1264 L<[perl #128607]|https://rt.perl.org/Public/Bug/Display.html?id=128607>
1268 Removed obsolete documentation of L<C<study()>|perlfunc/study>.
1278 Add C<pTHX_> to magic method examples.
1288 Document Tab VS Space.
1292 =head3 L<perlinterp>
1298 L<perlinterp> has been expanded to give a more detailed example of how to
1299 hunt around in the parser for how a given operator is handled.
1303 =head3 L<perllocale>
1309 Document C<NUL> collation handling.
1313 Some locales aren't compatible with Perl. Note the potential bad
1314 consequences of using them.
1318 =head3 L<perlmodinstall>
1324 All references to Usenet have been removed.
1328 =head3 L<perlmodlib>
1334 Updated the mirror list.
1338 All references to Usenet have been removed.
1342 =head3 L<perlnewmod>
1348 All references to Usenet have been removed.
1358 Added a section on calling methods using their fully qualified names.
1362 Do not discourage manual @ISA.
1376 Mention C<Moo> more.
1386 Clarify behavior single quote regexps.
1396 Several minor enhancements to the documentation.
1406 Fixed link to Crosby paper on hash complexity attack.
1416 Documented new feature: See L</Declaring a reference to a variable> above.
1426 Updated documentation of C<scalar(%hash)>. See L</scalar(%hash) return
1427 signature changed> above.
1431 =head3 L<perlunicode>
1437 Documented change to C<\p{I<script>}> to now use the improved Script_Extensions
1438 property. See L</Use of \p{script} uses the improved Script_Extensions
1443 Updated the text to correspond with changes in Unicode UTS#18, concerning
1444 regular expressions, and Perl compatibility with what it says.
1454 Removed obsolete documentation of C<${^ENCODING}>. See L</${^ENCODING} has
1455 been removed> above.
1459 Document C<@ISA>. Was documented other places, not not in L<perlvar>.
1465 =head2 New Diagnostics
1473 Since C<.> is now removed from C<@INC> by default, C<do> will now trigger
1474 a warning recommending to fix the C<do> statement:
1476 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"?>
1480 Using the empty pattern (which re-executes the last successfully-matched
1481 pattern) inside a code block in another regex, as in C</(?{ s!!new! })/>, has
1482 always previously yielded a segfault. It now produces an error:
1483 L<Infinite recursion in regex|perldiag/"Infinite recursion in regex">.
1487 L<The experimental declared_refs feature is not enabled|perldiag/"The experimental declared_refs feature is not enabled">
1489 (F) To declare references to variables, as in C<my \%x>, you must first enable
1492 no warnings "experimental::declared_refs";
1493 use feature "declared_refs";
1497 L<Version control conflict marker|perldiag/"Version control conflict marker">
1499 (F) The parser found a line starting with C<E<lt>E<lt>E<lt>E<lt>E<lt>E<lt>E<lt>>,
1500 C<E<gt>E<gt>E<gt>E<gt>E<gt>E<gt>E<gt>>, or C<=======>. These may be left by a
1501 version control system to mark conflicts after a failed merge operation.
1505 L<%s: command not found|perldiag/"%s: command not found">
1507 (A) You've accidentally run your script through B<bash> or another shell
1508 instead of Perl. Check the #! line, or manually feed your script into
1509 Perl yourself. The #! line at the top of your file could look like:
1515 L<%s: command not found: %s|perldiag/"%s: command not found: %s">
1517 (A) You've accidentally run your script through B<zsh> or another shell
1518 instead of Perl. Check the #! line, or manually feed your script into
1519 Perl yourself. The #! line at the top of your file could look like:
1525 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/">
1527 Unescaped left braces are already illegal in some contexts in regular
1528 expression patterns, but, due to an oversight, no deprecation warning
1529 was raised in other contexts where they are intended to become illegal.
1530 This warning is now raised in these contexts.
1534 L<Bareword in require contains "%s"|perldiag/"Bareword in require contains "%s"">
1538 L<Bareword in require maps to empty filename|perldiag/"Bareword in require maps to empty filename">
1542 L<Bareword in require maps to disallowed filename "%s"|perldiag/"Bareword in require maps to disallowed filename "%s"">
1546 L<Bareword in require must not start with a double-colon: "%s"|perldiag/"Bareword in require must not start with a double-colon: "%s"">
1556 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">
1558 See L</Deprecations>
1562 L<Declaring references is experimental|perldiag/"Declaring references is experimental">
1564 (S experimental::declared_refs) This warning is emitted if you use a reference
1565 constructor on the right-hand side of C<my()>, C<state()>, C<our()>, or
1566 C<local()>. Simply suppress the warning if you want to use the feature, but
1567 know that in doing so you are taking the risk of using an experimental feature
1568 which may change or be removed in a future Perl version:
1570 no warnings "experimental::declared_refs";
1571 use feature "declared_refs";
1576 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">
1578 (D deprecated) The special variable C<${^ENCODING}>, formerly used to implement
1579 the C<encoding> pragma, is no longer supported as of Perl 5.26.0.
1583 Since C<.> is now removed from C<@INC> by default, C<do> will now trigger
1584 a warning recommending to fix the C<do> statement:
1586 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"?>
1590 =head2 Changes to Existing Diagnostics
1596 When a C<require> fails, we now do not provide C<@INC> when the C<require>
1597 is for a file instead of a module.
1601 When C<@INC> is not scanned for a C<require> call, we no longer display
1602 C<@INC> to avoid confusion.
1606 Attribute "locked" is deprecated, and will disappear in Perl 5.28
1610 Attribute "unique" is deprecated, and will disappear in Perl 5.28
1614 Constants from lexical variables potentially modified elsewhere are
1615 deprecated. This will not be allowed in Perl 5.32
1619 Deprecated use of my() in false conditional. This will be a fatal error
1624 dump() better written as CORE::dump(). dump() will no longer be available
1629 ${^ENCODING} is no longer supported. Its use will be fatal in Perl 5.28
1633 File::Glob::glob() will disappear in perl 5.30. Use File::Glob::bsd_glob()
1638 %s() is deprecated on :utf8 handles. This will be a fatal error in Perl 5.30
1642 $* is no longer supported. Its use will be fatal in Perl 5.30
1646 $* is no longer supported. Its use will be fatal in Perl 5.30
1650 Opening dirhandle %s also as a file. This will be a fatal error in Perl 5.28
1654 Opening filehandle %s also as a directory. This will be a fatal
1659 Setting $/ to a reference to %s as a form of slurp is deprecated,
1660 treating as undef. This will be fatal in Perl 5.28
1664 Unescaped left brace in regex is deprecated here (and will be fatal
1665 in Perl 5.30), passed through in regex; marked by S<< E<lt>-- HERE >> in m/%s/
1669 Unknown charname '' is deprecated. Its use will be fatal in Perl 5.28
1673 Use of bare E<lt>E<lt> to mean E<lt>E<lt>"" is deprecated. Its use will be fatal in Perl 5.28
1677 Use of code point 0x%s is deprecated; the permissible max is 0x%s.
1678 This will be fatal in Perl 5.28
1682 Use of comma-less variable list is deprecated. Its use will be fatal
1687 Use of inherited AUTOLOAD for non-method %s() is deprecated. This
1688 will be fatal in Perl 5.28
1692 Use of strings with code points over 0xFF as arguments to %s operator
1693 is deprecated. This will be a fatal error in Perl 5.28
1697 Improve error for missing tie() package/method. This brings the error messages
1698 in line with the ones used for normal method calls, despite not using
1703 Make the sysread()/syswrite/() etc :utf8 handle warnings default. These
1704 warnings were under 'deprecated' previously.
1708 'do' errors now refer to 'do' (not 'require').
1712 Details as to the exact problem have been added to the diagnostics that
1713 occur when malformed UTF-8 is encountered when trying to convert to a
1718 Executing C<undef $x> where C<$x> is tied or magical no longer incorrectly
1719 blames the variable for an uninitialized-value warning encountered by the
1724 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/">
1726 The word "here" has been added to the message that was raised in
1727 v5.25.1. This is to indicate that there are contexts in which unescaped
1728 left braces are not (yet) illegal.
1732 Code like C<$x = $x . "a"> was incorrectly failing to yield a
1733 L<use of uninitialized value|perldiag/"Use of uninitialized value%s">
1734 warning when C<$x> was a lexical variable with an undefined value. That has
1735 now been fixed. [perl #127877]
1739 When the error "Experimental push on scalar is now forbidden" is raised for
1740 the hash functions C<keys>, C<each>, and C<values>, it is now followed by
1741 the more helpful message, "Type of arg 1 to whatever must be hash or
1742 array". [perl #127976]
1746 C<undef *_; shift> or C<undef *_; pop> inside a subroutine, with no
1747 argument to C<shift> or C<pop>, began crashing in Perl 5.14.0, but has now
1752 C<< "string$scalar-E<gt>$*" >> now correctly prefers concat overloading to
1753 string overloading if C<< $scalar-E<gt>$* >> returns an overloaded object,
1754 bringing it into consistency with C<$$scalar>.
1758 C<< /@0{0*-E<gt>@*/*0 >> and similar contortions used to crash, but no longer
1759 do, but merely produce a syntax error. [perl #128171]
1763 C<do> or C<require> with a reference or typeglob which, when stringified,
1764 contains a null character started crashing in Perl 5.20.0, but has now been
1765 fixed. [perl #128182]
1769 =head1 Utility Changes
1771 =head2 F<c2ph> and F<pstruct>
1777 These old utilities have long since superceded by L<h2xs>, and are
1778 now gone from the distribution.
1782 =head2 F<Porting/pod_lib.pl>
1788 Removed spurious executable bit.
1792 Account for possibility of DOS file endings.
1796 =head2 F<Porting/sync-with-cpan>
1806 =head2 F<perf/benchmarks>
1812 Tidy file, rename some symbols.
1816 =head2 F<Porting/checkAUTHORS.pl>
1822 Replace obscure character range with \w.
1826 =head2 F<t/porting/regen.t>
1832 try to be more helpful when tests fail.
1836 =head2 F<utils/h2xs.PL>
1842 Avoid infinite loop for enums.
1852 Long lines in the message body are now wrapped at 900 characters, to stay
1853 well within the 1000-character limit imposed by SMTP mail transfer agents.
1854 This is particularly likely to be important for the list of arguments to
1855 C<Configure>, which can readily exceed the limit if, for example, it names
1856 several non-default installation paths. This change also adds the first unit
1857 tests for perlbug. [perl #128020]
1861 =head1 Configuration and Compilation
1867 C<-Ddefault_inc_excludes_dot> has been turned on by default.
1871 The C<dtrace> build process has further changes:
1877 If the C<-xnolibs> is available, use that so a F<dtrace> perl can be
1878 built within a FreeBSD jail.
1882 On systems that build a dtrace object file (FreeBSD, Solaris and
1883 SystemTap's dtrace emulation), copy the input objects to a separate
1884 directory and process them there, and use those objects in the link,
1885 since C<dtrace -G> also modifies these objects.
1889 Add libelf to the build on FreeBSD 10.x, since dtrace adds references
1894 Generate a dummy dtrace_main.o if C<dtrace -G> fails to build it. A
1895 default build on Solaris generates probes from the unused inline
1896 functions, while they don't on FreeBSD, which causes C<dtrace -G> to
1905 You can now disable perl's use of the PERL_HASH_SEED and
1906 PERL_PERTURB_KEYS environment variables by configuring perl with
1907 C<-Accflags=NO_PERL_HASH_ENV>.
1911 You can now disable perl's use of the PERL_HASH_SEED_DEBUG environment
1912 variable by configuring perl with
1913 C<-Accflags=-DNO_PERL_HASH_SEED_DEBUG>.
1917 Zero out the alignment bytes when calculating the bytes for 80-bit C<NaN>
1918 and C<Inf> to make builds more reproducible. [perl #130133]
1922 Since 5.18 for testing purposes we have included support for
1923 building perl with a variety of non-standard, and non-recommended
1924 hash functions. Since we do not recommend the use of these functions
1925 we have removed them and their corresponding build options. Specifically
1926 this includes the following build options:
1930 PERL_HASH_FUNC_SUPERFAST
1931 PERL_HASH_FUNC_MURMUR3
1932 PERL_HASH_FUNC_ONE_AT_A_TIME
1933 PERL_HASH_FUNC_ONE_AT_A_TIME_OLD
1934 PERL_HASH_FUNC_MURMUR_HASH_64A
1935 PERL_HASH_FUNC_MURMUR_HASH_64B
1939 Remove "Warning: perl appears in your path"
1941 This install warning is more or less obsolete, since most platforms already
1942 *will* have a /usr/bin/perl or similar provided by the OS.
1946 Reduce verbosity of "make install.man"
1948 Previously, two progress messages were emitted for each manpage: one by
1949 installman itself, and one by the function in install_lib.pl that it calls to
1950 actually install the file. Disabling the second of those in each case saves
1951 over 750 lines of unhelpful output.
1955 Cleanup for clang -Weverything support. [perl 129961]
1959 Configure: signbit scan was assuming too much, stop assuming negative 0.
1963 Various compiler warnings have been silenced.
1967 Several smaller changes have been made to remove impediments to compiling under
1972 Builds using C<USE_PAD_RESET> now work again; this configuration had
1977 A probe for C<gai_strerror> was added to F<Configure> that checks if the
1978 the gai_strerror() routine is available and can be used to
1979 translate error codes returned by getaddrinfo() into human
1984 F<Configure> now aborts if both "-Duselongdouble" and "-Dusequadmath" are
1986 L<[perl #126203]|https://rt.perl.org/Public/Bug/Display.html?id=126203>
1990 Fixed a bug in which F<Configure> could append "-quadmath" to the archname even
1991 if it was already present.
1992 L<[perl #128538]|https://rt.perl.org/Public/Bug/Display.html?id=128538>
1996 Clang builds with "-DPERL_GLOBAL_STRUCT" or "-DPERL_GLOBAL_STRUCT_PRIVATE" have
1997 been fixed (by disabling Thread Safety Analysis for these configurations).
2001 F<make_ext.pl> no longer updates a module's F<pm_to_blib> file when no
2002 files require updates. This could cause dependencies, F<perlmain.c>
2003 in particular, to be rebuilt unnecessarily. [perl #126710]
2007 The output of C<perl -V> has been reformatted so that each configuration
2008 and compile-time option is now listed one per line, to improve
2013 C<Configure> now builds C<miniperl> and C<generate_uudmap> if you
2014 invoke it with C<-Dusecrosscompiler> but not C<-Dtargethost=somehost>.
2015 This means you can supply your target platform C<config.sh>, generate
2016 the headers and proceed to build your cross-target perl. [perl #127234]
2020 Builds with C<-Accflags=-DPERL_TRACE_OPS> now only dump the operator
2021 counts when the environment variable C<PERL_TRACE_OPS> to be set to a
2022 non-zero integer. This allows C<make test> to pass on such a build.
2026 When building with GCC 6 and link-time optimization (the C<-flto> option to
2027 C<gcc>), C<Configure> was treating all probed symbols as present on the
2028 system, regardless of whether they actually exist. This has been fixed.
2033 The F<t/test.pl> library is used for internal testing of Perl itself, and
2034 also copied by several CPAN modules. Some of those modules must work on
2035 older versions of Perl, so F<t/test.pl> must in turn avoid newer Perl
2036 features. Compatibility with Perl 5.8 was inadvertently removed some time
2037 ago; it has now been restored. [perl #128052]
2041 The build process no longer emits an extra blank line before building each
2042 "simple" extension (those with only F<*.pm> and F<*.pod> files).
2052 F<XS-APItest/t/utf8.t>: Several small fixes and enhancements.
2056 Tests for locales were erroneously using locales incompatible with Perl.
2060 Some parts of the test suite that try to exhaustively test edge cases in the
2061 regex implementation have been restricted to running for a maximum of five
2062 minutes. On slow systems they could otherwise take several hours, without
2063 significantly improving our understanding of the correctness of the code
2066 In addition, some of those test cases have been split into more files, to
2067 allow them to be run in parallel on suitable systems.
2071 A new internal facility allows analysing the time taken by the individual
2072 tests in Perl's own test suite; see F<Porting/harness-timer-report.pl>.
2076 F<t/re/regexp_nonull.t> has been added to test that the regular expression
2077 engine can handle scalars that do not have a null byte just past the end of
2082 A new test script, F<t/op/decl-refs.t>, has been added to test the new feature,
2083 "Declaring a reference to a variable".
2087 A new test script, F<t/re/anyof.t>, has been added to test that the ANYOF nodes
2088 generated by bracketed character classes are as expected.
2092 F<t/harness> now tries really hard not to run tests outside of the Perl
2093 source tree. [perl #124050]
2097 =head1 Platform Support
2099 =head2 New Platforms
2105 Perl now compiles under NetBSD on VAX machines. However, it's not
2106 possible for that platform to implement floating-point infinities and
2107 NaNs compatibly with most modern systems, which implement the IEEE-754
2108 floating point standard. The hexadecimal floating point (C<0x...p[+-]n>
2109 literals, C<printf %a>) is not implemented, either.
2110 The C<make test> passes 98% of tests.
2116 Test fixes and minor updates.
2120 Account for lack of C<inf>, C<nan>, and C<-0.0> support.
2126 =head2 Platform-Specific Notes
2132 don't treat -Dprefix=/usr as special, instead require an extra option
2133 -Ddarwin_distribution to produce the same results.
2137 Finish removing POSIX deprecated functions.
2141 OS X El Capitan doesn't implement the clock_gettime() or clock_getres() APIs,
2142 emulate them as necessary.
2146 Deprecated syscall(2) on macOS 10.12.
2150 Several tests have been updated to work (or be skipped) on EBCDIC platforms.
2154 L<Net::Ping> UDP test is skipped on HP-UX.
2158 The hints for Hurd have been improved enabling malloc wrap and reporting the
2159 GNU libc used (previously it was an empty string when reported).
2163 VAX floating point formats are now supported.
2171 The path separator for the C<PERL5LIB> and C<PERLLIB> environment entries is
2172 now a colon (C<:>) when running under a Unix shell. There is no change when
2173 running under DCL (it's still C<|>).
2177 Remove some VMS-specific hacks from C<showlex.t>. These were added 15 years
2178 ago, and are no longer necessary for any VMS version now supported.
2182 Move C<_pDEPTH> and C<_aDEPTH> after F<config.h> otherwise DEBUGGING
2183 may not be defined yet.
2187 VAXC has not been a possibility for a good long while, and the versions of the
2188 DEC/Compaq/HP/VSI C compiler that report themselves as "DEC" in a listing file
2189 are 15 years or more out-of-date and can be safely desupported.
2199 Support for compiling perl on Windows using Microsoft Visual Studio 2015
2200 (containing Visual C++ 14.0) has been added.
2202 This version of VC++ includes a completely rewritten C run-time library, some
2203 of the changes in which mean that work done to resolve a socket close() bug in
2204 perl #120091 and perl #118059 is not workable in its current state with this
2205 version of VC++. Therefore, we have effectively reverted that bug fix for
2206 VS2015 onwards on the basis that being able to build with VS2015 onwards is
2207 more important than keeping the bug fix. We may revisit this in the future to
2208 attempt to fix the bug again in a way that is compatible with VS2015.
2210 These changes do not affect compilation with GCC or with Visual Studio versions
2211 up to and including VS2013, i.e. the bug fix is retained (unchanged) for those
2214 Note that you may experience compatibility problems if you mix a perl built
2215 with GCC or VS E<lt>= VS2013 with XS modules built with VS2015, or if you mix a
2216 perl built with VS2015 with XS modules built with GCC or VS E<lt>= VS2013.
2217 Some incompatibility may arise because of the bug fix that has been reverted
2218 for VS2015 builds of perl, but there may well be incompatibility anyway because
2219 of the rewritten CRT in VS2015 (e.g. see discussion at
2220 http://stackoverflow.com/questions/30412951).
2230 Tweaks for Win32 VC vs GCC detection makefile code. This fixes issue that CCHOME
2231 depends on CCTYPE, which in auto detect mode is set after CCHOME, so CCHOME uses
2232 the uninit CCTYPE var. Also fix else vs .ELSE in makefile.mk
2236 fp definitions have been updated.
2242 Fix some breakage, add 'undef' value for default_inc_excludes_dot in build
2247 Drop support for Linux a.out Linux has used ELF for over twenty years.
2251 OpenBSD 6 still does not support returning pid, gid or uid with SA_SIGINFO.
2252 Make sure this is accounted for.
2256 t/uni/overload.t: Skip hanging test on FreeBSD.
2260 =head1 Internal Changes
2266 The C<op_class()> API function has been added. This is like the existing
2267 C<OP_CLASS()> macro, but can more accurately determine what struct an op
2268 has been allocated as. For example C<OP_CLASS()> might return
2269 C<OA_BASEOP_OR_UNOP> indicating that ops of this type are usually
2270 allocated as an C<OP> or C<UNOP>; while C<op_class()> will return
2271 C<OPclass_BASEOP> or C<OPclass_UNOP> as appropriate.
2275 The output format of the C<op_dump()> function (as used by C<perl -Dx>)
2276 has changed: it now displays an "ASCII-art" tree structure, and shows more
2277 low-level details about each op, such as its address and class.
2281 New versions of macros like C<isALPHA_utf8> and C<toLOWER_utf8> have
2282 been added, each with the
2283 suffix C<_safe>, like C<isSPACE_utf8_safe>. These take an extra
2284 parameter, giving an upper limit of how far into the string it is safe
2285 to read. Using the old versions could cause attempts to read beyond the
2286 end of the input buffer if the UTF-8 is not well-formed, and their use
2287 now raises a deprecation warning. Details are at
2288 L<perlapi/Character classification>.
2292 Calling macros like C<isALPHA_utf8> on malformed UTF-8 have issued a
2293 deprecation warning since Perl v5.18. They now die.
2294 Similarly, macros like C<toLOWER_utf8> on malformed UTF-8 now die.
2298 Calling the functions C<utf8n_to_uvchr> and its derivatives, while
2299 passing a string length of 0 is now asserted against in DEBUGGING
2300 builds, and otherwise returns the Unicode REPLACEMENT CHARACTER. If
2301 you have nothing to decode, you shouldn't call the decode function.
2305 The functions C<utf8n_to_uvchr> and its derivatives now return the
2306 Unicode REPLACEMENT CHARACTER if called with UTF-8 that has the overlong
2307 malformation, and that malformation is allowed by the input parameters.
2308 This malformation is where the UTF-8 looks valid syntactically, but
2309 there is a shorter sequence that yields the same code point. This has
2310 been forbidden since Unicode version 3.1.
2314 The functions C<utf8n_to_uvchr> and its derivatives now accept an input
2315 flag to allow the overflow malformation. This malformation is when the
2316 UTF-8 may be syntactically valid, but the code point it represents is
2317 not capable of being represented in the word length on the platform.
2318 What "allowed" means in this case is that the function doesn't return an
2319 error, and advances the parse pointer to beyond the UTF-8 in question,
2320 but it returns the Unicode REPLACEMENT CHARACTER as the value of the
2321 code point (since the real value is not representable).
2325 The C<PADOFFSET> type has changed from being unsigned to signed, and
2326 several pad-related variables such as C<PL_padix> have changed from being
2327 of type C<I32> to type C<PADOFFSET>.
2331 The function C<L<perlapi/utf8n_to_uvchr>> has been changed to not
2332 abandon searching for other malformations when the first one is
2333 encountered. A call to it thus can generate multiple diagnostics,
2334 instead of just one.
2338 A new function, C<L<perlapi/utf8n_to_uvchr_error>>, has been added for
2339 use by modules that need to know the details of UTF-8 malformations
2340 beyond pass/fail. Previously, the only ways to know why a sequence was
2341 ill-formed was to capture and parse the generated diagnostics, or to do
2346 Several new functions for handling Unicode have been added to the API:
2347 C<L<perlapi/is_strict_utf8_string>>,
2348 C<L<perlapi/is_c9strict_utf8_string>>,
2349 C<L<perlapi/is_utf8_string_flags>>,
2350 C<L<perlapi/is_strict_utf8_string_loc>>,
2351 C<L<perlapi/is_strict_utf8_string_loclen>>,
2352 C<L<perlapi/is_c9strict_utf8_string_loc>>,
2353 C<L<perlapi/is_c9strict_utf8_string_loclen>>,
2354 C<L<perlapi/is_utf8_string_loc_flags>>,
2355 C<L<perlapi/is_utf8_string_loclen_flags>>,
2356 C<L<perlapi/is_utf8_fixed_width_buf_flags>>,
2357 C<L<perlapi/is_utf8_fixed_width_buf_loc_flags>>,
2358 C<L<perlapi/is_utf8_fixed_width_buf_loclen_flags>>.
2360 These functions are all extensions of the C<is_utf8_string_*()> functions,
2361 that apply various restrictions to the UTF-8 recognized as valid.
2365 A new API function C<sv_setvpv_bufsize()> allows simultaneously setting the
2366 length and allocated size of the buffer in an C<SV>, growing the buffer if
2371 A new API macro C<SvPVCLEAR()> sets its C<SV> argument to an empty string,
2372 like Perl-space C<$x = ''>, but with several optimisations.
2376 All parts of the internals now agree that the C<sassign> op is a C<BINOP>;
2377 previously it was listed as a C<BASEOP> in F<regen/opcodes>, which meant
2378 that several parts of the internals had to be special-cased to accommodate
2379 it. This oddity's original motivation was to handle code like C<$x ||= 1>;
2380 that is now handled in a simpler way.
2384 Several new internal C macros have been added that take a string literal as
2385 arguments, alongside existing routines that take the equivalent value as two
2386 arguments, a character pointer and a length. The advantage of this is that
2387 the length of the string is calculated automatically, rather than having to
2388 be done manually. These routines are now used where appropriate across the
2393 The code in F<gv.c> that determines whether a variable has a special meaning
2394 to Perl has been simplified.
2398 The C<DEBUGGING>-mode output for regex compilation and execution has been
2403 Several macros and functions have been added to the public API for
2404 dealing with Unicode and UTF-8-encoded strings. See
2405 L<perlapi/Unicode Support>.
2409 Use C<my_strlcat()> in C<locale.c>. While C<strcat()> is safe in this context,
2410 some compilers were optimizing this to C<strcpy()> causing a porting test to
2411 fail that looks for unsafe code. Rather than fighting this, we just use
2412 C<my_strlcat()> instead.
2416 Three new ops, C<OP_ARGELEM>, C<OP_ARGDEFELEM> and C<OP_ARGCHECK> have
2417 been added. These are intended principally to implement the individual
2418 elements of a subroutine signature, plus any overall checking required.
2422 Perl no longer panics when switching into some locales on machines with
2423 buggy C<strxfrm()> implementations in their libc. [perl #121734]
2427 Perl is now built with the C<PERL_OP_PARENT> compiler define enabled by
2428 default. To disable it, use the C<PERL_NO_OP_PARENT> compiler define.
2429 This flag alters how the C<op_sibling> field is used in C<OP> structures,
2430 and has been available optionally since perl 5.22.0.
2432 See L<perl5220delta/"Internal Changes"> for more details of what this
2437 The meanings of some internal SV flags have been changed
2439 OPpRUNTIME, SVpbm_VALID, SVpbm_TAIL, SvTAIL_on, SvTAIL_off, SVrepl_EVAL,
2444 Change C<hv_fetch(…, "…", …, …)> to C<hv_fetchs(…, "…", …)>
2446 The dual-life dists all use Devel::PPPort, so they can use this function even
2447 though it was only added in 5.10.
2451 =head1 Selected Bug Fixes
2457 C< $-{$name} > would leak an C<AV> on each access if the regular
2458 expression had no named captures. The same applies to access to any
2459 hash tied with L<Tie::Hash::NamedCapture> and C<< all =E<gt> 1 >>. [perl
2464 Attempting to use the deprecated variable C<$#> as the object in an
2465 indirect object method call could cause a heap use after free or
2466 buffer overflow. [perl #129274]
2470 When checking for an indirect object method call in some rare cases
2471 the parser could reallocate the line buffer but then continue to use
2472 pointers to the old buffer. [perl #129190]
2476 Supplying a glob as the format argument to L<perlfunc/formline> would
2477 cause an assertion failure. [perl #130722]
2481 Code like C< $value1 =~ qr/.../ ~~ $value2 > would have the match
2482 converted into a qr// operator, leaving extra elements on the stack to
2483 confuse any surrounding expression. [perl #130705]
2487 Since 5.24.0 in some obscure cases, a regex which included code blocks
2488 from multiple sources (e.g. via embedded via qr// objects) could end up
2489 with the wrong current pad and crash or give weird results. [perl #129881]
2493 Occasionally C<local()>s in a code block within a patterns weren't being
2494 undone when the pattern matching backtracked over the code block.
2499 Using C<substr()> to modify a magic variable could access freed memory
2500 in some cases. [perl #129340]
2504 Perl 5.25.9 was fixed so that under C<use utf8>, the entire Perl program
2505 is checked that the UTF-8 is wellformed. It turns out that several edge
2506 cases were missed, and are now fixed. [perl #126310] was the original
2511 Under C<use utf8>, the entire Perl program is now checked that the UTF-8
2512 is wellformed. This resolves [perl #126310].
2516 The range operator C<..> on strings now handles its arguments correctly when in
2517 the scope of the L<< C<unicode_strings>|feature/"The 'unicode_strings' feature" >>
2518 feature. The previous behaviour was sufficiently unexpected that we believe no
2519 correct program could have made use of it.
2523 The S<split> operator did not ensure enough space was allocated for
2524 its return value in scalar context. It could then write a single
2525 pointer immediately beyond the end of the memory block allocated for
2526 the stack. [perl #130262]
2530 Using a large code point with the C<W> pack template character with
2531 the current output position aligned at just the right point could
2532 cause a write a single zero byte immediately beyond the end of an
2533 allocated buffer. [perl #129149]
2537 Supplying the form picture argument as part of the form argument list
2538 where the picture specifies modifying the argument could cause an
2539 access to the new freed compiled form. [perl #129125]
2543 Fix a problem with sort's build-in compare, where it would not sort
2544 correctly with 64-bit integers, and non-long doubles. [perl #130335]
2548 Fix issues with /(?{ ... E<lt>E<lt>EOF })/ that broke Method-Signatures. [perl #130398]
2552 Fix a macro which caused syntax error on an EBCDIC build.
2556 Prevent tests from getting hung up on 'NonStop' option. [perl #130445]
2560 Fixed an assertion failure with C<chop> and C<chomp>, which
2561 could be triggered by C<chop(@x =~ tr/1/1/)>. [perl #130198].
2565 Fixed a comment skipping error under C</x>; it could stop skipping a
2566 byte early, which could be in the middle of a UTF-8 character.
2571 F<perldb> now ignores F</dev/tty> on non-Unix systems. [perl #113960];
2575 Fix assertion failure for C<{}-E<gt>$x> when C<$x> isn't defined. [perl #130496].
2579 DragonFly BSD now has support for setproctitle(). [perl #130068].
2583 Fix an assertion error which could be triggered when lookahead string
2584 in patterns exceeded a minimum length. [perl #130522].
2588 Only warn once per literal about a misplaced C<_>. [perl #70878].
2592 Ensure range-start is set after error in C<tr///>. [perl #129342].
2596 Don't read past start of string for unmatched backref; otherwise,
2597 we may have heap buffer overflow. [perl #129377].
2601 Properly recognize mathematical digit ranges starting at U+1D7E.
2602 C<use re 'strict'> is supposed to warn if you use a range whose start
2603 and end digit aren't from the same group of 10. It didn't do that
2604 for five groups of mathematical digits starting at U+1D7E.
2608 A sub containing a "forward" declaration with the same name (e.g.,
2609 C<sub c { sub c; }>) could sometimes crash or loop infinitely. [perl
2614 A crash in executing a regex with a floating UTF-8 substring against a
2615 target string that also used UTF-8 has been fixed. [perl #129350]
2619 Previously, a shebang line like C<#!perl -i u> could be erroneously
2620 interpreted as requesting the C<-u> option. This has been fixed. [perl
2625 The regex engine was previously producing incorrect results in some rare
2626 situations when backtracking past a trie that matches only one thing; this
2627 showed up as capture buffers (C<$1>, C<$2>, etc) erroneously containing data
2628 from regex execution paths that weren't actually executed for the final
2629 match. [perl #129897]
2633 Certain regexes making use of the experimental C<regex_sets> feature could
2634 trigger an assertion failure. This has been fixed. [perl #129322]
2638 Invalid assignments to a reference constructor (e.g., C<\eval=time>) could
2639 sometimes crash in addition to giving a syntax error. [perl #125679]
2643 The parser could sometimes crash if a bareword came after C<evalbytes>.
2648 Autoloading via a method call would warn erroneously ("Use of inherited
2649 AUTOLOAD for non-method") if there was a stub present in the package into
2650 which the invocant had been blessed. The warning is no longer emitted in
2651 such circumstances. [perl #47047]
2655 A sub containing with a "forward" declaration with the same name (e.g.,
2656 C<sub c { sub c; }>) could sometimes crash or loop infinitely. [perl
2661 The use of C<splice> on arrays with nonexistent elements could cause other
2662 operators to crash. [perl #129164]
2666 Fixed case where C<re_untuit_start> will overshoot the length of a utf8
2667 string. [perl #129012]
2671 Handle C<CXt_SUBST> better in C<Perl_deb_stack_all>, previously it wasn't
2672 checking that the I<current> C<cx> is the right type, and instead was always
2673 checking the base C<cx> (effectively a noop). [perl #129029]
2677 Fixed two possible use-after-free bugs in C<Perl_yylex>. C<Perl_yylex>
2678 maintains up to two pointers into the parser buffer, one of which can
2679 become stale under the right conditions. [perl #129069]
2683 Fixed a crash with C<s///l> where it thought it was dealing with UTF-8
2684 when it wasn't. [perl #129038]
2688 Fixed place where regex was not setting the syntax error correctly.
2693 The C<&.> operator (and the C<&> operator, when it treats its arguments as
2694 strings) were failing to append a trailing null byte if at least one string
2695 was marked as utf8 internally. Many code paths (system calls, regexp
2696 compilation) still expect there to be a null byte in the string buffer
2697 just past the end of the logical string. An assertion failure was the
2698 result. [perl #129287]
2702 Check C<pack_sockaddr_un()>'s return value because C<pack_sockaddr_un()>
2703 silently truncates the supplied path if it won't fit into the C<sun_path>
2704 member of C<sockaddr_un>. This may change in the future, but for now
2705 check the path in theC<sockaddr> matches the desired path, and skip if
2706 it doesn't. [perl #128095]
2710 Make sure C<PL_oldoldbufptr> is preserved in C<scan_heredoc()>. In some
2711 cases this is used in building error messages. [perl #128988]
2715 Check for null PL_curcop in IN_LC() [perl #129106]
2719 Fixed the parser error handling for an 'C<:attr(foo>' that does not have
2724 Fix C<Perl_delimcpy()> to handle a backslash as last char, this
2725 actually fixed two bugs, [perl #129064] and [perl #129176].
2729 [perl #129267] rework gv_fetchmethod_pvn_flags separator parsing to
2730 prevent possible string overrun with invalid len in gv.c
2734 Problems with in-place array sorts: code like C<@a = sort { ... } @a>,
2735 where the source and destination of the sort are the same plain array, are
2736 optimised to do less copying around. Two side-effects of this optimisation
2737 were that the contents of C<@a> as visible to to sort routine were
2738 partially sorted, and under some circumstances accessing C<@a> during the
2739 sort could crash the interpreter. Both these issues have been fixed, and
2740 Sort functions see the original value of C<@a>.
2744 Non-ASCII string delimiters are now reported correctly in error messages
2745 for unterminated strings. [perl #128701]
2749 C<pack("p", ...)> used to emit its warning ("Attempt to pack pointer to
2750 temporary value") erroneously in some cases, but has been fixed.
2754 C<@DB::args> is now exempt from "used once" warnings. The warnings only
2755 occurred under B<-w>, because F<warnings.pm> itself uses C<@DB::args>
2760 The use of built-in arrays or hash slices in a double-quoted string no
2761 longer issues a warning ("Possible unintended interpolation...") if the
2762 variable has not been mentioned before. This affected code like
2763 C<qq|@DB::args|> and C<qq|@SIG{'CHLD', 'HUP'}|>. (The special variables
2764 C<@-> and C<@+> were already exempt from the warning.)
2768 C<gethostent> and similar functions now perform a null check internally, to
2769 avoid crashing with torsocks. This was a regression from 5.22. [perl
2774 C<defined *{'!'}>, C<defined *{'['}>, and C<defined *{'-'}> no longer leak
2775 memory if the typeglob in question has never been accessed before.
2779 Mentioning the same constant twice in a row (which is a syntax error) no
2780 longer fails an assertion under debugging builds. This was a regression
2781 from 5.20. [perl #126482]
2785 Many issues relating to C<printf "%a"> of hexadecimal floating point
2786 were fixed. In addition, the "subnormals" (formerly known as "denormals")
2787 floating point anumbers are now supported both with the plain IEEE 754
2788 floating point numbers (64-bit or 128-bit) and the x86 80-bit
2789 "extended precision". Note that subnormal hexadecimal floating
2790 point literals will give a warning about "exponent underflow".
2791 [perl #128843, #128889, #128890, #128893, #128909, #128919]
2795 A regression in 5.24 with C<tr/\N{U+...}/foo/> when the code point was between
2796 128 and 255 has been fixed. [perl #128734].
2800 A regression from the previous development release, 5.23.3, where
2801 compiling a regular expression could crash the interpreter has been
2802 fixed. [perl #128686].
2806 Use of a string delimiter whose code point is above 2**31 now works
2807 correctly on platforms that allow this. Previously, certain characters,
2808 due to truncation, would be confused with other delimiter characters
2809 with special meaning (such as C<?> in C<m?...?>), resulting
2810 in inconsistent behaviour. Note that this is non-portable,
2811 and is based on Perl's extension to UTF-8, and is probably not
2812 displayable nor enterable by any editor. [perl #128738]
2816 C<@{x> followed by a newline where C<x> represents a control or non-ASCII
2817 character no longer produces a garbled syntax error message or a crash.
2822 An assertion failure with C<%: = 0> has been fixed.
2823 L<[perl #128238]|https://rt.perl.org/Public/Bug/Display.html?id=128238>
2827 In Perl 5.18, the parsing of C<"$foo::$bar"> was accidentally changed, such
2828 that it would be treated as C<$foo."::".$bar>. The previous behavior, which
2829 was to parse it as C<$foo:: . $bar>, has been restored.
2830 L<[perl #128478]|https://rt.perl.org/Public/Bug/Display.html?id=128478>
2834 Since Perl 5.20, line numbers have been off by one when perl is invoked with
2835 the B<-x> switch. This has been fixed.
2836 L<[perl #128508]|https://rt.perl.org/Public/Bug/Display.html?id=128508>
2840 Vivifying a subroutine stub in a deleted stash (e.g., C<delete $My::{"Foo::"};
2841 \&My::Foo::foo>) no longer crashes. It had begun crashing in Perl 5.18.
2842 L<[perl #128532]|https://rt.perl.org/Public/Bug/Display.html?id=128532>
2846 Some obscure cases of subroutines and file handles being freed at the same time
2847 could result in crashes, but have been fixed. The crash was introduced in Perl
2849 L<[perl #128597]|https://rt.perl.org/Public/Bug/Display.html?id=128597>
2853 Code that looks for a variable name associated with an uninitialized value
2854 could cause an assertion in cases where magic is involved, such as
2855 C<$ISA[0][0]>. This has now been fixed.
2856 L<[perl #128253]|https://rt.perl.org/Public/Bug/Display.html?id=128253>
2860 A crash caused by code generating the warning "Subroutine STASH::NAME
2861 redefined" in cases such as C<sub P::f{} undef *P::; *P::f =sub{};> has been
2862 fixed. In these cases, where the STASH is missing, the warning will now appear
2863 as "Subroutine NAME redefined".
2864 L<[perl #128257]|https://rt.perl.org/Public/Bug/Display.html?id=128257>
2868 Fixed an assertion triggered by some code that handles deprecated behavior in
2869 formats, e.g. in cases like this:
2875 L<[perl #128255]|https://rt.perl.org/Public/Bug/Display.html?id=128255>
2879 A possible divide by zero in string transformation code on Windows has been
2880 avoided, fixing a crash when collating an empty string.
2881 L<[perl #128618]|https://rt.perl.org/Public/Bug/Display.html?id=128618>
2885 Some regular expression parsing glitches could lead to assertion failures with
2886 regular expressions such as C</(?E<lt>=/> and C</(?E<lt>!/>. This has now been fixed.
2887 L<[perl #128170]|https://rt.perl.org/Public/Bug/Display.html?id=128170>
2891 C< until ($x = 1) { ... } > and C< ... until $x = 1 > now properly
2892 warn when syntax warnings are enabled. [perl #127333]
2896 socket() now leaves the error code returned by the system in C<$!> on
2897 failure. [perl #128316]
2901 Assignment variants of any bitwise ops under the C<bitwise> feature would
2902 crash if the left-hand side was an array or hash. [perl #128204]
2906 C<require> followed by a single colon (as in C<foo() ? require : ...> is
2907 now parsed correctly as C<require> with implicit $_, rather than
2908 C<require "">. [perl #128307]
2912 Scalar C<keys %hash> can now be assigned to consistently in all scalar
2913 lvalue contexts. Previously it worked for some contexts but not others.
2917 List assignment to C<vec> or C<substr> with an array or hash for its first
2918 argument used to result in crashes or "Can't coerce" error messages at run
2919 time, unlike scalar assignment, which would give an error at compile time.
2920 List assignment now gives a compile-time error, too. [perl #128260]
2924 Expressions containing an C<&&> or C<||> operator (or their synonyms C<and>
2925 and C<or>) were being compiled incorrectly in some cases. If the left-hand
2926 side consisted of either a negated bareword constant or a negated C<do {}>
2927 block containing a constant expression, and the right-hand side consisted of
2928 a negated non-foldable expression, one of the negations was effectively
2929 ignored. The same was true of C<if> and C<unless> statement modifiers,
2930 though with the left-hand and right-hand sides swapped. This long-standing
2931 bug has now been fixed. [perl #127952]
2935 C<reset> with an argument no longer crashes when encountering stash entries
2936 other than globs. [perl #128106]
2940 Assignment of hashes to, and deletion of, typeglobs named C<*::::::> no
2941 longer causes crashes. [perl #128086]
2945 Handle SvIMMORTALs in LHS of list assign. [perl #129991]
2949 [perl #130010] a5540cf breaks texinfo
2951 This involved user-defined Unicode properties.
2955 Fix error message for unclosed C<\N{> in regcomp.
2957 An unclosed C<\N{> could give the wrong error message
2958 C<"\N{NAME} must be resolved by the lexer">.
2962 List assignment in list context where the LHS contained aggregates and
2963 where there were not enough RHS elements, used to skip scalar lvalues.
2964 Previously, C<(($a,$b,@c,$d) = (1))> in list context returned C<($a)>; now
2965 it returns C<($a,$b,$d)>. C<(($a,$b,$c) = (1))> is unchanged: it still
2966 returns C<($a,$b,$c)>. This can be seen in the following:
2968 sub inc { $_++ for @_ }
2969 inc(($a,$b,@c,$d) = (10))
2971 Formerly, the values of C<($a,$b,$d)> would be left as C<(11,undef,undef)>;
2972 now they are C<(11,1,1)>.
2978 The basic problem is that code like this: /(?{ s!!! })/ can trigger infinite
2979 recursion on the C stack (not the normal perl stack) when the last successful
2980 pattern in scope is itself. Since the C stack overflows this manifests as an
2981 untrappable error/segfault, which then kills perl.
2983 We avoid the segfault by simply forbidding the use of the empty pattern when it
2984 would resolve to the currently executing pattern.
2988 [perl 128997] Avoid reading beyond the end of the line buffer when there's a
2989 short UTF-8 character at the end.
2993 [perl 129950] fix firstchar bitmap under utf8 with prefix optimisation.
2997 [perl 129954] Carp/t/arg_string.t: be liberal in f/p formats.
3001 [perl 129928] make do "a\0b" fail silently instead of throwing.
3005 [perl 129130] make chdir allocate the stack it needs.
3009 =head1 Known Problems
3015 Some modules have been broken by the L<context stack rework|/Internal Changes>.
3016 These modules were relying on non-guaranteed implementation details in perl.
3017 Their maintainers have been informed, and should contact perl5-porters for
3018 advice if needed. Below is a subset of these modules:
3022 =item * L<Algorithm::Permute>
3026 L<Coro> and perl v5.22.0 were already incompatible due to a change in the perl,
3027 and the reworking on the perl context stack creates a further incompatibility.
3028 perl5-porters has L<discussed the issue on the mailing
3029 list|http://www.nntp.perl.org/group/perl.perl5.porters/2016/05/msg236174.html>.
3031 =item * L<Data::Alias>
3035 =item * L<Scope::Upper>
3043 The module L<lexical::underscore> no longer works on perl v5.24.0, because perl
3044 no longer has a lexical C<$_>!
3048 C<mod_perl> has been patched for compatibility for v5.22.0 and later but no
3049 release has been made. The relevant patch (and other changes) can be found in
3050 their source code repository, L<mirrored at
3051 GitHub|https://github.com/apache/mod_perl/commit/82827132efd3c2e25cc413c85af61bb63375da6e>.
3055 =head1 Errata From Previous Releases
3061 Parsing bad POSIX charclasses no longer leaks memory. This was fixed in Perl
3063 L<[perl #128313]|https://rt.perl.org/Public/Bug/Display.html?id=128313>
3067 Fixed issues with recursive regexes. The behavior was fixed in Perl 5.24.0.
3068 L<[perl #126182]|https://rt.perl.org/Public/Bug/Display.html?id=126182>
3074 Jon Portnoy (AVENJ), a prolific Perl author and admired Gentoo community
3075 member, has passed away on August 10, 2016. He will be remembered and
3076 missed by all those with which he came in contact and enriched with his
3077 intellect, wit, and spirit.
3079 It is with great sadness we also note Kip Hampton's passing.. Probably
3080 best known as the author of the Perl & XML column on XML.com, he was a
3081 core contributor to AxKit, an XML server platform that became an Apache
3082 Foundation project. He was a frequent speaker in the early days at
3083 OSCON, and most recently at YAPC::NA in Madison. He was frequently on
3084 irc.perl.org as `ubu`, generally in the #axkit-dahut community, the
3085 group responsible for YAPC::NA Asheville in 2011.
3087 Kip and his constant contributions to the community will be greatly
3090 =head1 Acknowledgements
3092 Perl 5.26.0 represents approximately 12 months of development since Perl 5.24.0
3093 and contains approximately 370,000 lines of changes across 2,600 files from 86
3096 Excluding auto-generated files, documentation and release tools, there were
3097 approximately 230,000 lines of changes to 1,800 .pm, .t, .c and .h files.
3099 Perl continues to flourish into its third decade thanks to a vibrant community
3100 of users and developers. The following people are known to have contributed the
3101 improvements that became Perl 5.24.1:
3103 Aaron Crane, Abigail, Ævar Arnfjörð Bjarmason, Alex Vandiver, Andreas
3104 König, Andreas Voegele, Andrew Fresh, Andy Lester, Aristotle Pagaltzis, Chad
3105 Granum, Chase Whitener, Chris 'BinGOs' Williams, Chris Lamb, Christian Hansen,
3106 Christian Millour, Colin Newell, Craig A. Berry, Dagfinn Ilmari Mannsåker, Dan
3107 Collins, Daniel Dragan, Dave Cross, Dave Rolsky, David Golden, David H.
3108 Gutteridge, David Mitchell, Dominic Hargreaves, Doug Bell, E. Choroba, Ed Avis,
3109 Father Chrysostomos, François Perrad, Hauke D, H.Merijn Brand, Hugo van der
3110 Sanden, Ivan Pozdeev, James E Keenan, James Raspass, Jarkko Hietaniemi, Jerry
3111 D. Hedden, Jim Cromie, J. Nick Koston, John Lightsey, Karen Etheridge, Karl
3112 Williamson, Leon Timmermans, Lukas Mai, Matthew Horsfall, Maxwell Carey, Misty
3113 De Meo, Neil Bowers, Nicholas Clark, Nicolas R., Niko Tyni, Pali, Paul
3114 Marquess, Peter Avalos, Petr Písař, Pino Toscano, Rafael Garcia-Suarez, Reini
3115 Urban, Renee Baecker, Ricardo Signes, Richard Levitte, Rick Delaney, Salvador
3116 Fandiño, Samuel Thibault, Sawyer X, Sébastien Aperghis-Tramoni, Sergey
3117 Aleynikov, Shlomi Fish, Smylers, Stefan Seifert, Steffen Müller, Stevan
3118 Little, Steve Hay, Steven Humphrey, Sullivan Beck, Theo Buehler, Thomas Sibley,
3119 Todd Rinaldo, Tomasz Konojacki, Tony Cook, Unicode Consortium, Yaroslav Kuzmin,
3122 The list above is almost certainly incomplete as it is automatically generated
3123 from version control history. In particular, it does not include the names of
3124 the (very much appreciated) contributors who reported issues to the Perl bug
3127 Many of the changes included in this version originated in the CPAN modules
3128 included in Perl's core. We're grateful to the entire CPAN community for
3129 helping Perl to flourish.
3131 For a more complete list of all of Perl's historical contributors, please see
3132 the F<AUTHORS> file in the Perl source distribution.
3134 =head1 Reporting Bugs
3136 If you find what you think is a bug, you might check the articles recently
3137 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
3138 L<https://rt.perl.org/> . There may also be information at
3139 L<http://www.perl.org/> , the Perl Home Page.
3141 If you believe you have an unreported bug, please run the L<perlbug> program
3142 included with your release. Be sure to trim your bug down to a tiny but
3143 sufficient test case. Your bug report, along with the output of C<perl -V>,
3144 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
3146 If the bug you are reporting has security implications which make it
3147 inappropriate to send to a publicly archived mailing list, then see
3148 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
3149 for details of how to report the issue.
3153 The F<Changes> file for an explanation of how to view exhaustive details on
3156 The F<INSTALL> file for how to build Perl.
3158 The F<README> file for general stuff.
3160 The F<Artistic> and F<Copying> files for copyright information.