diff options
Diffstat (limited to 'pod/perldelta.pod')
| -rw-r--r-- | pod/perldelta.pod | 426 |
1 files changed, 277 insertions, 149 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod index 10182f1a64..e76912aa47 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -2,280 +2,408 @@ =head1 NAME -perldelta - what is new for perl v5.35.10 +[ 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.35.11 =head1 DESCRIPTION -This document describes differences between the 5.35.9 release and the 5.35.10 +This document describes differences between the 5.35.10 release and the 5.35.11 release. -If you are upgrading from an earlier release such as 5.35.8, first read -L<perl5359delta>, which describes differences between 5.35.8 and 5.35.9. +If you are upgrading from an earlier release such as 5.35.9, first read +L<perl53510delta>, which describes differences between 5.35.9 and 5.35.10. + +=head1 Notice + +XXX Any important notices here =head1 Core Enhancements -=head2 New function C<builtin::trim> +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 L</Performance Enhancements> section. + +[ List each enhancement as a =head2 entry ] + +=head1 Security + +XXX Any security-related notices go here. In particular, any security +vulnerabilities closed should be noted here rather than in the +L</Selected Bug Fixes> section. + +[ List each security issue as a =head2 entry ] + +=head1 Incompatible Changes + +XXX For a release on a stable branch, this section aspires to be: -This function treats its argument as a string, returning the result of -removing all white space at its beginning and ending. See -L<builtin/trim> + 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. -=head2 Variable length lookbehind is mostly no longer considered experimental. +[ List each incompatible change as a =head2 entry ] -Prior to this release any form of variable length lookbehind was -considered experimental. With this release the experimental status has -been reduced to cover only lookbehind that contains capturing parenthesis. -This is because it is not clear if +=head1 Deprecations - "aaz"=~/(?=z)(?<=(a|aa))/ +XXX Any deprecated features, syntax, modules etc. should be listed here. -should match and leave $1 equaling "a" or "aa". Currently it will match -the longest possible alternative, "aa". We are confident that the overall -construct will now match only when it should, we are not confident that we -will keep the current "longest match" behavior. +=head2 Module removals -=head2 Added 'builtin::indexed' +XXX Remove this section if not applicable. -A new function has been added to the C<builtin> package, called C<indexed>. -It returns a list twice as big as its argument list, where each item is -preceded by its index within that list. This is primarily useful for using -the new C<foreach> syntax with multiple iterator variables to iterate over -an array or list, while also tracking the index of each item: +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. - use builtin 'indexed'; +The core versions of these modules will now issue C<"deprecated">-category +warnings to alert you to this fact. To silence these deprecation warnings, +install the modules in question from CPAN. - foreach my ($index, $val) (indexed @array) { - ... - } +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. -=head2 Added experimental feature 'extra_paired_delimiters' +=over -Perl traditionally has allowed just four pairs of string/pattern -delimiters: S<C<( )>> S<C<{ }>> S<C<[ ]>> and S<C<< < > >>>, all in the -ASCII range. Unicode has hundreds more possibilities, and using this -feature enables many of them. When enabled, you can say S<C<qr« »>> for -example, or S<C<use utf8; <q𝄃string𝄂>>. See -L<feature/The 'extra_paired_delimiters' feature> for -details. +=item XXX + +XXX Note that deprecated modules should be listed here even if they are listed +as an updated module in the L</Modules and Pragmata> section. + +=back + +[ List each other deprecation as a =head2 entry ] =head1 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 ] + =over 4 =item * -Large hashes no longer allocate their keys from the shared string table. +XXX + +=back + +=head1 Modules and Pragmata + +XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/> +go here. If Module::CoreList is updated, generate an initial draft of the +following sections using F<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 F<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.) -The same internal datatype (C<PVHV>) is used for all of +[ Within each section, list entries as an =item entry ] + +=head2 New Modules and Pragmata =over 4 =item * -Symbol tables +XXX Remove this section if not applicable. -=item * +=back + +=head2 Updated Modules and Pragmata -Objects (by default) +=over 4 =item * -Associative arrays +L<XXX> has been upgraded from version A.xx to B.yy. + +If there was something important to note about this change, include that here. =back -The shared string table was originally added to improve performance for blessed -hashes used as objects, because every object instance has the same keys, so it -is an optimisation to share memory between them. It also makes sense for symbol -tables, where derived classes will have the same keys (typically method names), -and the OP trees built for method calls can also share memory. The shared -string table behaves roughly like a cache for hash keys. - -But for hashes actually used as associative arrays - mapping keys to values - -typically the keys are not re-used in other hashes. For example, "seen" hashes -are keyed by object IDs (or addresses), and logically these keys won't repeat -in other hashes. - -Storing these "used just once" keys in the shared string table increases CPU -and RAM use for no gain. For such keys the shared string table behaves as a -cache with a 0% hit rate. Storing all the keys there increases the total size -of the shared string table, as well as increasing the number of times it is -resized as it grows. B<Worse> - in any environment that has "copy on write" -memory for child process (such as a pre-forking server), the memory pages used -for the shared string table rapidly need to be copied as the child process -manipulates hashes. Hence if most of the shared string table is such keys that -are used only in one place, there is no benefit from re-use within the perl -interpreter, but a high cost due to more pages for the OS to copy. - -The perl interpreter now disables shared hash keys for "large" hashes (that are -neither objects nor symbol tables). "Large" is a heuristic - currently the -heuristic is that sharing is disabled when adding a key to a hash triggers -allocation of more storage, and the hash has more than 42 keys. - -This B<might> cause slightly increased memory usage for programs that create -(unblessed) data structures that contain multiple large hashes that share the -same keys. But generally our testing suggests that for the specific cases -described it is a win, and other code is unaffected. +=head2 Removed Modules and Pragmata + +=over 4 + +=item * + +XXX =back -=head1 Modules and Pragmata +=head1 Documentation -=head2 Updated Modules and Pragmata +XXX Changes to files in F<pod/> go here. Consider grouping entries by +file and be sure to link to the appropriate page, e.g. L<perlfunc>. + +=head2 New Documentation + +XXX Changes which create B<new> files in F<pod/> go here. + +=head3 L<XXX> + +XXX Description of the purpose of the new file here + +=head2 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 L<https://github.com/Perl/perl5/issues>. + +XXX Changes which significantly change existing files in F<pod/> go here. +However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics> +section. + +Additionally, the following selected changes have been made: + +=head3 L<XXX> =over 4 =item * -L<Attribute::Handlers> has been upgraded from version 1.01 to 1.02. +XXX Description of the change here -=item * +=back -L<B::Deparse> has been upgraded from version 1.62 to 1.63. +=head1 Diagnostics -=item * +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 L<perldiag>. -L<DB_File> has been upgraded from version 1.856 to 1.857. +XXX New or changed warnings emitted by the core's C<C> code go here. Also +include any changes in L<perldiag> that reconcile it to the C<C> code. -=item * +=head2 New Diagnostics -L<Devel::PPPort> has been upgraded from version 3.64 to 3.68. +XXX Newly added diagnostic messages go under here, separated into New Errors +and New Warnings -=item * +=head3 New Errors -L<experimental> has been upgraded from version 0.027 to 0.028. +=over 4 =item * -L<ExtUtils::ParseXS> has been upgraded from version 3.44 to 3.45. +XXX L<message|perldiag/"message"> -=item * +=back -L<ExtUtils::Typemaps> has been upgraded from version 3.44 to 3.45. +=head3 New Warnings + +=over 4 =item * -L<feature> has been upgraded from version 1.70 to 1.71. +XXX L<message|perldiag/"message"> -=item * +=back -L<File::Spec> has been upgraded from version 3.83 to 3.84. +=head2 Changes to Existing Diagnostics -=item * +XXX Changes (i.e. rewording) of diagnostic messages go here -L<GDBM_File> has been upgraded from version 1.22 to 1.23. +=over 4 =item * -L<Module::CoreList> has been upgraded from version 5.20220220 to 5.20220320. +XXX Describe change here -=item * +=back -L<Opcode> has been upgraded from version 1.56 to 1.57. +=head1 Utility Changes -=item * +XXX Changes to installed programs such as F<perldoc> and F<xsubpp> go here. +Most of these are built within the directory F<utils>. -L<Scalar::Util> has been upgraded from version 1.61 to 1.62. +[ List utility changes as a =head2 entry for each utility and =item +entries for each change +Use L<XXX> with program names to get proper documentation linking. ] -=item * +=head2 L<XXX> -L<Test::Simple> has been upgraded from version 1.302188 to 1.302190. +=over 4 =item * -L<warnings> has been upgraded from version 1.57 to 1.58. +XXX + +=back + +=head1 Configuration and Compilation + +XXX Changes to F<Configure>, F<installperl>, F<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 +L</Platform Support> section, instead. + +[ List changes as an =item entry ]. + +=over 4 =item * -L<XS::APItest> has been upgraded from version 1.21 to 1.22. +XXX =back -=head1 Documentation +=head1 Testing -=head2 Changes to Existing Documentation +XXX Any significant changes to the testing of a freshly built perl should be +listed here. Changes which create B<new> files in F<t/> go here as do any +large changes to the testing harness (e.g. when parallel testing was added). +Changes to existing files in F<t/> aren't worth summarizing, although the bugs +that they represent may be covered elsewhere. -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 L<https://github.com/Perl/perl5/issues>. +XXX If there were no significant test changes, say this: -=head1 Diagnostics +Tests were added and changed to reflect the other additions and changes +in this release. -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 L<perldiag>. +XXX If instead there were significant changes, say this: -=head2 New Diagnostics +Tests were added and changed to reflect the other additions and +changes in this release. Furthermore, these significant changes were +made: -=head3 New Errors +[ List each test improvement as an =item entry ] =over 4 =item * -L<Wide character in $0|perldiag/"Wide character in %s"> +XXX + +=back + +=head1 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. ] -Attempts to put wide characters into the program name (C<$0>) now -provoke this warning. +=head2 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 F<hints/> +directories, or new subdirectories and F<README> files at the top level of the +source tree. + +=over 4 + +=item XXX-some-platform + +XXX =back -=head2 Changes to Existing Diagnostics +=head2 Discontinued Platforms + +XXX List any platforms that this version of perl no longer compiles on. =over 4 -=item * New 'scalar' category for "Useless use of sort in scalar context" +=item XXX-some-platform -When C<sort> is used in scalar context, it provokes a warning that this is not -useful. This warning used to be in the C<void> category. A new category for -warnings about scalar context has now been added, called C<scalar>. +XXX + +=back + +=head2 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 +L</Modules and Pragmata> section. + +=over 4 + +=item XXX-some-platform + +XXX =back =head1 Internal Changes +XXX Changes which affect the interface available to C<XS> code go here. Other +significant internal changes for future core maintainers should be noted as +well. + +[ List each change as an =item entry ] + =over 4 =item * -C<sv_dump> (and L<Devel::Peek>’s C<Dump> function) now escapes high-bit -octets in the PV as hex rather than octal. Since most folks understand hex -more readily than octal, this should make these dumps a bit more legible. -This does B<not> affect any other diagnostic interfaces like C<pv_display>. +XXX =back -=head1 Acknowledgements +=head1 Selected Bug Fixes -Perl 5.35.10 represents approximately 4 weeks of development since Perl -5.35.9 and contains approximately 15,000 lines of changes across 300 files -from 26 authors. +XXX Important bug fixes in the core language are summarized here. Bug fixes in +files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>. -Excluding auto-generated files, documentation and release tools, there were -approximately 6,900 lines of changes to 190 .pm, .t, .c and .h files. +[ List each fix as an =item entry ] -Perl continues to flourish into its fourth decade thanks to a vibrant -community of users and developers. The following people are known to have -contributed the improvements that became Perl 5.35.10: +=over 4 + +=item * -Bernd, Brad Barden, Chad Granum, cuishuang, Curtis Poe, Dagfinn Ilmari -Mannsåker, Daniel Laügt, Felipe Gasper, Graham Knop, Hugo van der Sanden, -James E Keenan, Karl Williamson, Leon Timmermans, Matthew Horsfall, Michiel -Beijen, Nicholas Clark, Nicolas R, Paul Evans, Renee Baecker, Ricardo -Signes, Richard Leach, Sawyer X, Sisyphus, Steve Hay, TAKAI Kousuke, Yves -Orton. +XXX + +=back -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. +=head1 Known Problems + +XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any +tests that had to be C<TODO>ed for the release would be noted here. Unfixed +platform specific bugs also go here. + +[ List each fix as an =item entry ] + +=over 4 + +=item * + +XXX + +=back + +=head1 Errata From Previous Releases + +=over 4 + +=item * + +XXX Add anything here that we forgot to add, or were mistaken about, in +the perldelta of a previous release. + +=back + +=head1 Obituary + +XXX If any significant core contributor or member of the CPAN community has +died, add a short obituary here. + +=head1 Acknowledgements -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. +XXX Generate this with: -For a more complete list of all of Perl's historical contributors, please -see the F<AUTHORS> file in the Perl source distribution. + perl Porting/acknowledgements.pl v5.35.10..HEAD =head1 Reporting Bugs |