perl5242delta(1)

1PERL5242DELTA(1)       Perl Programmers Reference Guide       PERL5242DELTA(1)
2
3
4

NAME

6       perl5242delta - what is new for perl v5.24.2
7

DESCRIPTION

9       This document describes differences between the 5.24.1 release and the
10       5.24.2 release.
11
12       If you are upgrading from an earlier release such as 5.24.0, first read
13       perl5241delta, which describes differences between 5.24.0 and 5.24.1.
14

Security

16   Improved handling of '.' in @INC in base.pm
17       The handling of (the removal of) '.' in @INC in base has been improved.
18       This resolves some problematic behaviour in the approach taken in Perl
19       5.24.1, which is probably best described in the following two threads
20       on the Perl 5 Porters mailing list:
21       <http://www.nntp.perl.org/group/perl.perl5.porters/2016/08/msg238991.html>,
22       <http://www.nntp.perl.org/group/perl.perl5.porters/2016/10/msg240297.html>.
23
24   "Escaped" colons and relative paths in PATH
25       On Unix systems, Perl treats any relative paths in the PATH environment
26       variable as tainted when starting a new process.  Previously, it was
27       allowing a backslash to escape a colon (unlike the OS), consequently
28       allowing relative paths to be considered safe if the PATH was set to
29       something like "/\:.".  The check has been fixed to treat "." as
30       tainted in that example.
31

Modules and Pragmata

33   Updated Modules and Pragmata
34       ·   base has been upgraded from version 2.23 to 2.23_01.
35
36       ·   Module::CoreList has been upgraded from version 5.20170114_24 to
37           5.20170715_24.
38

Selected Bug Fixes

40       ·   Fixed a crash with "s///l" where it thought it was dealing with
41           UTF-8 when it wasn't.  [perl #129038]
42           <https://rt.perl.org/Ticket/Display.html?id=129038>
43

Acknowledgements

45       Perl 5.24.2 represents approximately 6 months of development since Perl
46       5.24.1 and contains approximately 2,500 lines of changes across 53
47       files from 18 authors.
48
49       Excluding auto-generated files, documentation and release tools, there
50       were approximately 960 lines of changes to 17 .pm, .t, .c and .h files.
51
52       Perl continues to flourish into its third decade thanks to a vibrant
53       community of users and developers.  The following people are known to
54       have contributed the improvements that became Perl 5.24.2:
55
56       Aaron Crane, Abigail, Aristotle Pagaltzis, Chris 'BinGOs' Williams, Dan
57       Collins, David Mitchell, Eric Herman, Father Chrysostomos, James E
58       Keenan, Karl Williamson, Lukas Mai, Renee Baecker, Ricardo Signes,
59       Sawyer X, Stevan Little, Steve Hay, Tony Cook, Yves Orton.
60
61       The list above is almost certainly incomplete as it is automatically
62       generated from version control history.  In particular, it does not
63       include the names of the (very much appreciated) contributors who
64       reported issues to the Perl bug tracker.
65
66       Many of the changes included in this version originated in the CPAN
67       modules included in Perl's core.  We're grateful to the entire CPAN
68       community for helping Perl to flourish.
69
70       For a more complete list of all of Perl's historical contributors,
71       please see the AUTHORS file in the Perl source distribution.
72

Reporting Bugs

74       If you find what you think is a bug, you might check the articles
75       recently posted to the comp.lang.perl.misc newsgroup and the perl bug
76       database at <https://rt.perl.org/> .  There may also be information at
77       <http://www.perl.org/> , the Perl Home Page.
78
79       If you believe you have an unreported bug, please run the perlbug
80       program included with your release.  Be sure to trim your bug down to a
81       tiny but sufficient test case.  Your bug report, along with the output
82       of "perl -V", will be sent off to perlbug@perl.org to be analysed by
83       the Perl porting team.
84
85       If the bug you are reporting has security implications which make it
86       inappropriate to send to a publicly archived mailing list, then see
87       "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of
88       how to report the issue.
89