1=encoding utf8 2 3=head1 NAME 4 5perl5184delta - what is new for perl v5.18.4 6 7=head1 DESCRIPTION 8 9This document describes differences between the 5.18.4 release and the 5.18.2 10release. B<Please note:> This document ignores perl 5.18.3, a broken release 11which existed for a few hours only. 12 13If you are upgrading from an earlier release such as 5.18.1, first read 14L<perl5182delta>, which describes differences between 5.18.1 and 5.18.2. 15 16=head1 Modules and Pragmata 17 18=head2 Updated Modules and Pragmata 19 20=over 4 21 22=item * 23 24L<Digest::SHA> has been upgraded from 5.84_01 to 5.84_02. 25 26=item * 27 28L<perl5db.pl> has been upgraded from version 1.39_10 to 1.39_11. 29 30This fixes a crash in tab completion, where available. [perl #120827] Also, 31filehandle information is properly reset after a pager is run. [perl #121456] 32 33=back 34 35=head1 Platform Support 36 37=head2 Platform-Specific Notes 38 39=over 4 40 41=item Win32 42 43=over 4 44 45=item * 46 47Introduced by 48L<[GH #12161]|https://github.com/Perl/perl5/issues/12161>, a memory 49leak on every call to C<system> and backticks (C< `` >), on most Win32 Perls 50starting from 5.18.0 has been fixed. The memory leak only occurred if you 51enabled pseudo-fork in your build of Win32 Perl, and were running that build on 52Server 2003 R2 or newer OS. The leak does not appear on WinXP SP3. 53L<[GH #13741]|https://github.com/Perl/perl5/issues/13741> 54 55=back 56 57=back 58 59=head1 Selected Bug Fixes 60 61=over 4 62 63=item * 64 65The debugger now properly resets filehandles as needed. [perl #121456] 66 67=item * 68 69A segfault in Digest::SHA has been addressed. [perl #121421] 70 71=item * 72 73perl can again be built with USE_64_BIT_INT, with Visual C 2003, 32 bit. 74[perl #120925] 75 76=item * 77 78A leading { (brace) in formats is properly parsed again. [perl #119973] 79 80=item * 81 82Copy the values used to perturb hash iteration when cloning an 83interpreter. This was fairly harmless but caused C<valgrind> to 84complain. [perl #121336] 85 86=item * 87 88In Perl v5.18 C<undef *_; goto &sub> and C<local *_; goto &sub> started 89crashing. This has been fixed. [perl #119949] 90 91=back 92 93=head1 Acknowledgements 94 95Perl 5.18.4 represents approximately 9 months of development since Perl 5.18.2 96and contains approximately 2,000 lines of changes across 53 files from 13 97authors. 98 99Perl continues to flourish into its third decade thanks to a vibrant community 100of users and developers. The following people are known to have contributed the 101improvements that became Perl 5.18.4: 102 103Daniel Dragan, David Mitchell, Doug Bell, Father Chrysostomos, Hiroo Hayashi, 104James E Keenan, Karl Williamson, Mark Shelor, Ricardo Signes, Shlomi Fish, 105Smylers, Steve Hay, Tony Cook. 106 107The list above is almost certainly incomplete as it is automatically generated 108from version control history. In particular, it does not include the names of 109the (very much appreciated) contributors who reported issues to the Perl bug 110tracker. 111 112Many of the changes included in this version originated in the CPAN modules 113included in Perl's core. We're grateful to the entire CPAN community for 114helping Perl to flourish. 115 116For a more complete list of all of Perl's historical contributors, please see 117the F<AUTHORS> file in the Perl source distribution. 118 119=head1 Reporting Bugs 120 121If you find what you think is a bug, you might check the articles recently 122posted to the comp.lang.perl.misc newsgroup and the perl bug database at 123http://rt.perl.org/perlbug/ . There may also be information at 124http://www.perl.org/ , the Perl Home Page. 125 126If you believe you have an unreported bug, please run the L<perlbug> program 127included with your release. Be sure to trim your bug down to a tiny but 128sufficient test case. Your bug report, along with the output of C<perl -V>, 129will be sent off to perlbug@perl.org to be analysed by the Perl porting team. 130 131If the bug you are reporting has security implications, which make it 132inappropriate to send to a publicly archived mailing list, then please send it 133to perl5-security-report@perl.org. This points to a closed subscription 134unarchived mailing list, which includes all the core committers, who will be 135able to help assess the impact of issues, figure out a resolution, and help 136co-ordinate the release of patches to mitigate or fix the problem across all 137platforms on which Perl is supported. Please only use this address for 138security issues in the Perl core, not for modules independently distributed on 139CPAN. 140 141=head1 SEE ALSO 142 143The F<Changes> file for an explanation of how to view exhaustive details on 144what changed. 145 146The F<INSTALL> file for how to build Perl. 147 148The F<README> file for general stuff. 149 150The F<Artistic> and F<Copying> files for copyright information. 151 152=cut 153 154