perl5184delta(1)

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

NAME

6       perl5184delta - what is new for perl v5.18.4
7

DESCRIPTION

9       This document describes differences between the 5.18.4 release and the
10       5.18.2 release.  Please note:  This document ignores perl 5.18.3, a
11       broken release which existed for a few hours only.
12
13       If you are upgrading from an earlier release such as 5.18.1, first read
14       perl5182delta, which describes differences between 5.18.1 and 5.18.2.
15

Modules and Pragmata

17   Updated Modules and Pragmata
18       •   Digest::SHA has been upgraded from 5.84_01 to 5.84_02.
19
20       •   perl5db.pl has been upgraded from version 1.39_10 to 1.39_11.
21
22           This fixes a crash in tab completion, where available. [perl
23           #120827]  Also, filehandle information is properly reset after a
24           pager is run. [perl #121456]
25

Platform Support

27   Platform-Specific Notes
28       Win32
29           •   Introduced by [GH #12161]
30               <https://github.com/Perl/perl5/issues/12161>, a memory leak on
31               every call to "system" and backticks ( `` ), on most Win32
32               Perls starting from 5.18.0 has been fixed.  The memory leak
33               only occurred if you enabled pseudo-fork in your build of Win32
34               Perl, and were running that build on Server 2003 R2 or newer
35               OS.  The leak does not appear on WinXP SP3.  [GH #13741]
36               <https://github.com/Perl/perl5/issues/13741>
37

Selected Bug Fixes

39       •   The debugger now properly resets filehandles as needed. [perl
40           #121456]
41
42       •   A segfault in Digest::SHA has been addressed.  [perl #121421]
43
44       •   perl can again be built with USE_64_BIT_INT, with Visual C 2003, 32
45           bit.  [perl #120925]
46
47       •   A leading { (brace) in formats is properly parsed again. [perl
48           #119973]
49
50       •   Copy the values used to perturb hash iteration when cloning an
51           interpreter.  This was fairly harmless but caused "valgrind" to
52           complain. [perl #121336]
53
54       •   In Perl v5.18 "undef *_; goto &sub" and "local *_; goto &sub"
55           started crashing.  This has been fixed. [perl #119949]
56

Acknowledgements

58       Perl 5.18.4 represents approximately 9 months of development since Perl
59       5.18.2 and contains approximately 2,000 lines of changes across 53
60       files from 13 authors.
61
62       Perl continues to flourish into its third decade thanks to a vibrant
63       community of users and developers. The following people are known to
64       have contributed the improvements that became Perl 5.18.4:
65
66       Daniel Dragan, David Mitchell, Doug Bell, Father Chrysostomos, Hiroo
67       Hayashi, James E Keenan, Karl Williamson, Mark Shelor, Ricardo Signes,
68       Shlomi Fish, Smylers, Steve Hay, Tony Cook.
69
70       The list above is almost certainly incomplete as it is automatically
71       generated from version control history. In particular, it does not
72       include the names of the (very much appreciated) contributors who
73       reported issues to the Perl bug tracker.
74
75       Many of the changes included in this version originated in the CPAN
76       modules included in Perl's core. We're grateful to the entire CPAN
77       community for helping Perl to flourish.
78
79       For a more complete list of all of Perl's historical contributors,
80       please see the AUTHORS file in the Perl source distribution.
81

Reporting Bugs

83       If you find what you think is a bug, you might check the articles
84       recently posted to the comp.lang.perl.misc newsgroup and the perl bug
85       database at http://rt.perl.org/perlbug/ .  There may also be
86       information at http://www.perl.org/ , the Perl Home Page.
87
88       If you believe you have an unreported bug, please run the perlbug
89       program included with your release.  Be sure to trim your bug down to a
90       tiny but sufficient test case.  Your bug report, along with the output
91       of "perl -V", will be sent off to perlbug@perl.org to be analysed by
92       the Perl porting team.
93
94       If the bug you are reporting has security implications, which make it
95       inappropriate to send to a publicly archived mailing list, then please
96       send it to perl5-security-report@perl.org.  This points to a closed
97       subscription unarchived mailing list, which includes all the core
98       committers, who will be able to help assess the impact of issues,
99       figure out a resolution, and help co-ordinate the release of patches to
100       mitigate or fix the problem across all platforms on which Perl is
101       supported.  Please only use this address for security issues in the
102       Perl core, not for modules independently distributed on CPAN.
103