Abigail > perl > perldelta

Download:
perl-5.23.9.tar.bz2

Annotate this POD

Website

Source   Latest Release: perl-5.24.0-RC4

NAME ^

perldelta - what is new for perl v5.23.9

DESCRIPTION ^

This document describes differences between the 5.23.8 release and the 5.23.9 release.

If you are upgrading from an earlier release such as 5.23.7, first read perl5238delta, which describes differences between 5.23.7 and 5.23.8.

Core Enhancements ^

perl will now croak when closing an in-place output file fails

Until now, failure to close the output file for an in-place edit was not detected, meaning that the input file could be clobbered without the edit being successfully completed. Now, when the output file cannot be closed successfully, an exception is raised.

Security ^

Remove duplicate environment variables from environ

Previously, if an environment variable appeared more than once in environ[], %ENV would contain the last entry for that name, while a typical getenv() would return the first entry. We now make sure %ENV contains the same as what getenv returns.

Second, we remove duplicates from environ[], so if a setting with that name is set in %ENV we won't pass an unsafe value to a child process.

[CVE-2016-2381]

Performance Enhancements ^

Modules and Pragmata ^

Updated Modules and Pragmata

Documentation ^

Changes to Existing Documentation

perlfunc

Configuration and Compilation ^

Platform Support ^

Platform-Specific Notes

Win32
  • Building a 64-bit perl with a 64-bit GCC but a 32-bit gmake would result in an invalid $Config{archname} for the resulting perl. [perl #127584]
  • Errors set by Winsock functions are now put directly into $^E, and the relevant WSAE* error codes are now exported from the Errno and POSIX modules for testing this against.

    The previous behaviour of putting the errors (converted to POSIX-style E* error codes since Perl 5.20.0) into $! was buggy due to the non-equivalence of like-named Winsock and POSIX error constants, a relationship between which has unfortunately been established in one way or another since Perl 5.8.0.

    The new behaviour provides a much more robust solution for checking Winsock errors in portable software without accidentally matching POSIX tests that were intended for other OSes and may have different meanings for Winsock.

    The old behaviour is currently retained, warts and all, for backwards compatibility, but users are encouraged to change any code that tests $! against E* constants for Winsock errors to instead test $^E against WSAE* constants. After a suitable deprecation period, the old behaviour may be removed, leaving $! unchanged after Winsock function calls, to avoid any possible confusion over which error variable to check.

Selected Bug Fixes ^

Acknowledgements ^

Perl 5.23.9 represents approximately 4 weeks of development since Perl 5.23.8 and contains approximately 21,000 lines of changes across 230 files from 23 authors.

Excluding auto-generated files, documentation and release tools, there were approximately 8,500 lines of changes to 120 .pm, .t, .c and .h files.

Perl continues to flourish into its third decade thanks to a vibrant community of users and developers. The following people are known to have contributed the improvements that became Perl 5.23.9:

Abigail, Alex Vandiver, Andy Broad, Aristotle Pagaltzis, Chris 'BinGOs' Williams, Craig A. Berry, Dagfinn Ilmari Mannsåker, Daniel Dragan, David Mitchell, Father Chrysostomos, H.Merijn Brand, Jarkko Hietaniemi, John Peacock, Karl Williamson, Leon Timmermans, Lukas Mai, Matthew Horsfall, Ricardo Signes, Sawyer X, Shlomi Fish, Steve Hay, Tony Cook, Yves Orton.

The list above is almost certainly incomplete as it is automatically generated from version control history. In particular, it does not include the names of the (very much appreciated) contributors who reported issues to the Perl bug tracker.

Many of the changes included in this version originated in the CPAN modules included in Perl's core. We're grateful to the entire CPAN community for helping Perl to flourish.

For a more complete list of all of Perl's historical contributors, please see the AUTHORS file in the Perl source distribution.

Reporting Bugs ^

If you find what you think is a bug, you might check the articles recently posted to the comp.lang.perl.misc newsgroup and the perl bug database at https://rt.perl.org/ . There may also be information at http://www.perl.org/ , the Perl Home Page.

If you believe you have an unreported bug, please run the perlbug program included with your release. Be sure to trim your bug down to a tiny but sufficient test case. Your bug report, along with the output of perl -V, will be sent off to perlbug@perl.org to be analysed by the Perl porting team.

If the bug you are reporting has security implications, which make it inappropriate to send to a publicly archived mailing list, then please send it to perl5-security-report@perl.org. This points to a closed subscription unarchived mailing list, which includes all the core committers, who will be able to help assess the impact of issues, figure out a resolution, and help co-ordinate the release of patches to mitigate or fix the problem across all platforms on which Perl is supported. Please only use this address for security issues in the Perl core, not for modules independently distributed on CPAN.

SEE ALSO ^

The Changes file for an explanation of how to view exhaustive details on what changed.

The INSTALL file for how to build Perl.

The README file for general stuff.

The Artistic and Copying files for copyright information.

syntax highlighting: