Skip to content

Latest commit

 

History

History
508 lines (309 loc) · 13.4 KB

perldelta.pod

File metadata and controls

508 lines (309 loc) · 13.4 KB
Raw

NAME

[ this is a template for a new perldelta file. Any text flagged as XXX needs to be processed before release. ]

perldelta - what is new for perl v5.39.5

DESCRIPTION

This document describes differences between the 5.39.4 release and the 5.39.5 release.

If you are upgrading from an earlier release such as 5.39.3, first read perl5394delta, which describes differences between 5.39.3 and 5.39.4.

Notice

XXX Any important notices here

glibc has an undocumented feature to return the current locale when using the POSIX 2008 locale API. This feature is now experimentally enabled by default so as to see if there are problems with it. This enabling expires in v5.39.10. In the meantime, if you run into problems, open a bug ticket and Configure with -Accflags=-DNO_NL_LOCALE_NAME to turn it off.

Core Enhancements

XXX New core language features go here. Summarize user-visible core language enhancements. Particularly prominent performance optimisations could go here, but most should go in the "Performance Enhancements" section.

[ List each enhancement as a =head2 entry ]

Security

XXX Any security-related notices go here. In particular, any security vulnerabilities closed should be noted here rather than in the "Selected Bug Fixes" section.

[ List each security issue as a =head2 entry ]

Incompatible Changes

XXX For a release on a stable branch, this section aspires to be:

There are no changes intentionally incompatible with 5.XXX.XXX
If any exist, they are bugs, and we request that you submit a
report.  See L</Reporting Bugs> below.

[ List each incompatible change as a =head2 entry ]

Deprecations

XXX Any deprecated features, syntax, modules etc. should be listed here.

Module removals

XXX Remove this section if not applicable.

The following modules will be removed from the core distribution in a future release, and will at that time need to be installed from CPAN. Distributions on CPAN which require these modules will need to list them as prerequisites.

The core versions of these modules will now issue "deprecated"-category warnings to alert you to this fact. To silence these deprecation warnings, install the modules in question from CPAN.

Note that these are (with rare exceptions) fine modules that you are encouraged to continue to use. Their disinclusion from core primarily hinges on their necessity to bootstrapping a fully functional, CPAN-capable Perl installation, not usually on concerns over their design.

XXX

XXX Note that deprecated modules should be listed here even if they are listed as an updated module in the "Modules and Pragmata" section.

[ List each other deprecation as a =head2 entry ]

Performance Enhancements

XXX Changes which enhance performance without changing behaviour go here. There may well be none in a stable release.

[ List each enhancement as an =item entry ]

  • XXX

Modules and Pragmata

XXX All changes to installed files in cpan/, dist/, ext/ and lib/ go here. If Module::CoreList is updated, generate an initial draft of the following sections using Porting/corelist-perldelta.pl. A paragraph summary for important changes should then be added by hand. In an ideal world, dual-life modules would have a Changes file that could be cribbed.

The list of new and updated modules is modified automatically as part of preparing a Perl release, so the only reason to manually add entries here is if you're summarising the important changes in the module update. (Also, if the manually-added details don't match the automatically-generated ones, the release manager will have to investigate the situation carefully.)

[ Within each section, list entries as an =item entry ]

New Modules and Pragmata

  • XXX Remove this section if Porting/corelist-perldelta.pl did not add any content here.

Updated Modules and Pragmata

  • IO has been upgraded from version 1.53 to 1.54.

    Fixed IO::Handle/blocking on Windows, which has been non-functional since IO 1.32. [GH #17455]

  • builtin has been upgraded from version 0.011 to 0.012.

    Added the load_module() builtin function as per PPC 0006.

  • POSIX has been upgraded from version 2.16 to 2.17.

    Adjusted the signbit() on NaN test to handle the unusual bit pattern returned for NaN by Oracle Developer Studio's compiler. [GH #21533]

Removed Modules and Pragmata

  • XXX Remove this section if Porting/corelist-perldelta.pl did not add any content here.

Documentation

XXX Changes to files in pod/ go here. Consider grouping entries by file and be sure to link to the appropriate page, e.g. perlfunc.

New Documentation

XXX Changes which create new files in pod/ go here.

XXX

XXX Description of the purpose of the new file here

Changes to Existing Documentation

We have attempted to update the documentation to reflect the changes listed in this document. If you find any we have missed, open an issue at https://github.com/Perl/perl5/issues.

XXX Changes which significantly change existing files in pod/ go here. However, any changes to pod/perldiag.pod should go in the "Diagnostics" section.

Additionally, the following selected changes have been made:

XXX

  • XXX Description of the change here

Diagnostics

The following additions or changes have been made to diagnostic output, including warnings and fatal error messages. For the complete list of diagnostic messages, see perldiag.

XXX New or changed warnings emitted by the core's C code go here. Also include any changes in perldiag that reconcile it to the C code.

New Diagnostics

XXX Newly added diagnostic messages go under here, separated into New Errors and New Warnings

New Errors

New Warnings

Changes to Existing Diagnostics

XXX Changes (i.e. rewording) of diagnostic messages go here

  • XXX Describe change here

Utility Changes

XXX Changes to installed programs such as perldoc and xsubpp go here. Most of these are built within the directory utils.

[ List utility changes as a =head2 entry for each utility and =item entries for each change Use XXX with program names to get proper documentation linking. ]

XXX

  • XXX

Configuration and Compilation

XXX Changes to Configure, installperl, installman, and analogous tools go here. Any other changes to the Perl build process should be listed here. However, any platform-specific changes should be listed in the "Platform Support" section, instead.

[ List changes as an =item entry ].

  • XXX

Testing

XXX Any significant changes to the testing of a freshly built perl should be listed here. Changes which create new files in t/ go here as do any large changes to the testing harness (e.g. when parallel testing was added). Changes to existing files in t/ aren't worth summarizing, although the bugs that they represent may be covered elsewhere.

XXX If there were no significant test changes, say this:

Tests were added and changed to reflect the other additions and changes in this release.

XXX If instead there were significant changes, say this:

Tests were added and changed to reflect the other additions and changes in this release. Furthermore, these significant changes were made:

[ List each test improvement as an =item entry ]

  • porting/globvar.t now uses the more portable nm -P ... to fetch the names defined in an object file. The parsing of the names found in the object is now separated from processing them to handle the duplication between local and global definitions on AIX. [GH #21637]

  • A test was added to lib/locale_threads.t that extensively stress tests locale handling. It turns out that the libc implementations on various platforms have bugs in this regard, including Linux, Windows, *BSD derivatives including Darwin, and others. Experimental versions of this test have been used in the past few years to find bugs in the Perl implementation and in those platforms, as well as to develop workarounds in the Perl implementation, where feasible, for the platform bugs. Multiple bug report tickets have been filed against platforms, and some have been fixed. The test checks that platforms that purport to support thread-safe locale handling actually do so (and that perl works properly on those that do; The read-only variable ${^SAFE_LOCALES} is set to 1 if perl thinks the platform can handle this, whatever the platform's documentation says).

    Also tested for is if the various locale categories can indeed be set independently to disparate locales. (An example of where you might want to do this is if you are a Western Canadian living and working in Holland. You likely will want to have the LC_MONETARY locale be set to where you are living, but have the other parts of your locale retain your native English values. Later, as you get a bit more comfortable with Dutch, and in order to communicate better with your colleagues, you might want to change LC_TIME and LC_NUMERIC to Dutch, while leaving LC_CTYPE and LC_COLLATE set to English indefinitely.)

Platform Support

XXX Any changes to platform support should be listed in the sections below.

[ Within the sections, list each platform as an =item entry with specific changes as paragraphs below it. ]

New Platforms

XXX List any platforms that this version of perl compiles on, that previous versions did not. These will either be enabled by new files in the hints/ directories, or new subdirectories and README files at the top level of the source tree.

XXX-some-platform

XXX

Discontinued Platforms

XXX List any platforms that this version of perl no longer compiles on.

XXX-some-platform

XXX

Platform-Specific Notes

XXX List any changes for specific platforms. This could include configuration and compilation changes or changes in portability/compatibility. However, changes within modules for platforms should generally be listed in the "Modules and Pragmata" section.

Oracle Developer Studio (Solaris, Oracle Linux)

Due to an apparent code generation bug, the default optimization level for the Oracle Developer Studio (formerly Sun Workshop) compiler is now -xO1. [GH #21535]

Windows

Enable copysign, signbit, acosh, asinh, atanh, exp2, tgamma in the bundled configuration used for MSVC. [GH #21610]

The build process no longer supports Visual Studio 2013. This was failing to build at a very basic level and there has been no reports of such failures. [GH #21624]

Internal Changes

XXX Changes which affect the interface available to XS code go here. Other significant internal changes for future core maintainers should be noted as well.

[ List each change as an =item entry ]

  • XXX

Selected Bug Fixes

XXX Important bug fixes in the core language are summarized here. Bug fixes in files in ext/ and lib/ are best summarized in "Modules and Pragmata".

Include references to GitHub issues and PRs as: [GH #12345] and the release manager will later use a regex to expand these into links.

[ List each fix as an =item entry ]

  • XXX

Known Problems

XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any tests that had to be TODOed for the release would be noted here. Unfixed platform specific bugs also go here.

[ List each fix as an =item entry ]

  • XXX

Errata From Previous Releases

  • XXX Add anything here that we forgot to add, or were mistaken about, in the perldelta of a previous release.

Obituary

XXX If any significant core contributor or member of the CPAN community has died, add a short obituary here.

Acknowledgements

XXX Generate this with:

perl Porting/acknowledgements.pl v5.39.4..HEAD

Reporting Bugs

If you find what you think is a bug, you might check the perl bug database at https://github.com/Perl/perl5/issues. There may also be information at http://www.perl.org/, the Perl Home Page.

If you believe you have an unreported bug, please open an issue at https://github.com/Perl/perl5/issues. Be sure to trim your bug down to a tiny but sufficient test case.

If the bug you are reporting has security implications which make it inappropriate to send to a public issue tracker, then see "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of how to report the issue.

Give Thanks

If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you can do so by running the perlthanks program:

perlthanks

This will send an email to the Perl 5 Porters list with your show of thanks.

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.