perldelta - Updates, tidy-ups and remove boilerplate

1 files changed, 81 insertions, 291 deletions

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 3034bf1551..867cf59caa 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -2,9 +2,6 @@
 
 =head1 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.29.1
 
 =head1 DESCRIPTION
@@ -15,170 +12,139 @@ release.
 If you are upgrading from an earlier release such as 5.28.0, first read
 L<perl5290delta>, which describes differences between 5.28.0 and 5.29.0.
 
-=head1 Notice
-
-XXX Any important notices here
+=head1 Incompatible Changes
 
-=head1 Core Enhancements
+=head2 Delimiters must now be graphemes
 
-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.
+See L<perldeprecation/Use of unassigned code point or non-standalone grapheme
+for a delimiter.>
 
-[ List each enhancement as a =head2 entry ]
+=head2 Some formerly deprecated uses of an unescaped left brace C<"{"> in
+regular expression patterns are now illegal
 
-=head1 Security
+But to avoid breaking code unnecessarily, most instances that issued a
+deprecation warning, remain legal and now have a non-deprecation warning
+raised.  See L<perldeprecation/Unescaped left braces in regular expressions>.
 
-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.
+=head1 Performance Enhancements
 
-[ List each security issue as a =head2 entry ]
+=over 4
 
-=head1 Incompatible Changes
+=item *
 
-XXX For a release on a stable branch, this section aspires to be:
+Translating from UTF-8 into the code point it represents now is done via a
+deterministic finite automaton, speeding it up.  As a typical example,
+C<ord("\x7fff")> now requires 12% fewer instructions than before.  The
+performance of checking that a sequence of bytes is valid UTF-8 is similarly
+improved, again by using a dfa.
 
-    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.
+=back
 
-[ List each incompatible change as a =head2 entry ]
+=head1 Modules and Pragmata
 
-=head2 Delimiters must now be graphemes
+=head2 Updated Modules and Pragmata
 
-See L<perldeprecation/Use of unassigned code point or non-standalone grapheme for a delimiter.>
+=over 4
 
-=head2 Some formerly deprecated uses of an unescaped left brace C<"{">
-in regular expression patterns are now illegal
+=item *
 
-But to avoid breaking code unnecessarily, most instances that issued a
-deprecation warning, remain legal and now have a non-deprecation warning
-raised.  See L<perldeprecation/Unescaped left braces in regular
-expressions>.
+L<bignum> has been upgraded from version 0.49 to 0.50.
 
-=head1 Deprecations
+=item *
 
-XXX Any deprecated features, syntax, modules etc. should be listed here.
+L<Compress::Raw::Bzip2> has been upgraded from version 2.074 to 2.081.
 
-=head2 Module removals
+=item *
 
-XXX Remove this section if not applicable.
+L<Compress::Raw::Zlib> has been upgraded from version 2.076 to 2.081.
 
-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.
+=item *
 
-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.
+L<Config::Perl::V> has been upgraded from version 0.29 to 0.30.
 
-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.
+=item *
 
-=over
+L<DB_File> has been upgraded from version 1.840 to 1.842.
 
-=item XXX
+=item *
 
-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.
+L<Digest::SHA> has been upgraded from version 6.01 to 6.02.
 
-=back
+=item *
 
-[ List each other deprecation as a =head2 entry ]
+L<experimental> has been upgraded from version 0.019 to 0.020.
 
-=head1 Performance Enhancements
+=item *
 
-XXX Changes which enhance performance without changing behaviour go here.
-There may well be none in a stable release.
+L<ExtUtils::Manifest> has been upgraded from version 1.70 to 1.71.
 
-[ List each enhancement as an =item entry ]
+=item *
 
-=over 4
+L<File::Temp> has been upgraded from version 0.2304 to 0.2308.
 
 =item *
 
-Translating from UTF-8 into the code point it represents now is done via
-a deterministic finite automaton, speeding it up.  As a typical example,
-C<ord("\x7fff")> now requires 12% fewer instructions than before.
-The performance of checking that a sequence of bytes is valid UTF-8 is
-similarly improved, again by using a dfa.
-
-=back
+IO-Compress has been upgraded from version 2.074 to 2.081.
 
-=head1 Modules and Pragmata
+=item *
 
-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.
+L<IPC::Cmd> has been upgraded from version 1.00 to 1.02.
 
-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.)
+=item *
 
-[ Within each section, list entries as an =item entry ]
+L<Locale::Codes> has been upgraded from version 3.56 to 3.57.
 
-=head2 New Modules and Pragmata
+=item *
 
-=over 4
+L<Math::BigInt> has been upgraded from version 1.999811 to 1.999813.
 
 =item *
 
-XXX Remove this section if not applicable.
+L<Math::BigInt::FastCalc> has been upgraded from version 0.5006 to 0.5007.
 
-=back
+=item *
 
-=head2 Updated Modules and Pragmata
+L<Math::BigRat> has been upgraded from version 0.2613 to 0.2614.
 
-=over 4
+=item *
+
+L<parent> has been upgraded from version 0.236 to 0.237.
 
 =item *
 
-L<XXX> has been upgraded from version A.xx to B.yy.
+L<perlfaq> has been upgraded from version 5.021011 to 5.20180605.
 
-If there was something important to note about this change, include that here.
+=item *
 
-=back
+podlators has been upgraded from version 4.10 to 4.11.
 
-=head2 Removed Modules and Pragmata
+=item *
 
-=over 4
+L<Test::Simple> has been upgraded from version 1.302133 to 1.302138.
 
 =item *
 
-XXX
+L<Thread::Queue> has been upgraded from version 3.12 to 3.13.
 
-=back
+=item *
 
-=head1 Documentation
+L<Time::Local> has been upgraded from version 1.25 to 1.28.
 
-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>.
+=item *
 
-=head2 New Documentation
+L<version> has been upgraded from version 0.9923 to 0.9924.
 
-XXX Changes which create B<new> files in F<pod/> go here.
+If there was something important to note about this change, include that here.
 
-=head3 L<XXX>
+=back
 
-XXX Description of the purpose of the new file here
+=head1 Documentation
 
 =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, send email
-to L<perlbug@perl.org|mailto:perlbug@perl.org>.
-
-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.
+We have attempted to update the documentation to reflect the changes listed in
+this document.  If you find any we have missed, send email to
+L<perlbug@perl.org|mailto:perlbug@perl.org>.
 
 Additionally, the following selected changes have been made:
 
@@ -211,152 +177,29 @@ 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 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.
-
-=head2 New Diagnostics
-
-XXX Newly added diagnostic messages go under here, separated into New Errors
-and New Warnings
-
-=head3 New Errors
-
-=over 4
-
-=item *
-
-XXX L<message|perldiag/"message">
-
-=back
-
-=head3 New Warnings
-
-=over 4
-
-=item *
-
-XXX L<message|perldiag/"message">
-
-=back
-
 =head2 Changes to Existing Diagnostics
 
-XXX Changes (i.e. rewording) of diagnostic messages go here
-
-=over 4
-
-=item *
-
-XXX Describe change here
-
-=back
-
-=head1 Utility Changes
-
-XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
-Most of these are built within the directory F<utils>.
-
-[ 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. ]
-
-=head2 L<XXX>
-
-=over 4
-
-=item *
-
-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 *
 
-XXX
+As noted under L<Incompatible Changes> above, the deprecation warning
+"Unescaped left brace in regex is deprecated here (and will be fatal in Perl
+5.30), passed through in regex; marked by S<<-- HERE> in m/%s/" has been
+changed to the non-deprecation warning "Unescaped left brace in regex is passed
+through in regex; marked by S<<-- HERE> in m/%s/".
 
 =back
 
 =head1 Testing
 
-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.
-
-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 ]
-
-=over 4
-
-=item *
-
-XXX
-
-=back
+Tests were added and changed to reflect the other additions and changes in this
+release.
 
 =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. ]
-
-=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 Discontinued Platforms
-
-XXX List any platforms that this version of perl no longer compiles on.
-
-=over 4
-
-=item XXX-some-platform
-
-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 HP-UX 11.11
@@ -390,29 +233,8 @@ been added to the B<nmake> makefile.)
 
 =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 *
-
-XXX
-
-=back
-
 =head1 Selected Bug Fixes
 
-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>.
-
-[ List each fix as an =item entry ]
-
 =over 4
 
 =item *
@@ -429,38 +251,6 @@ L<[perl #133368]|https://rt.perl.org/Ticket/Display.html?id=133368>
 
 =back
 
-=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
 
 XXX Generate this with:
@@ -469,8 +259,8 @@ XXX Generate this with:
 
 =head1 Reporting Bugs
 
-If you find what you think is a bug, you might check the perl bug database
-at L<https://rt.perl.org/> .  There may also be information at
+If you find what you think is a bug, you might check the perl bug database at
+L<https://rt.perl.org/> .  There may also be information at
 L<http://www.perl.org/> , the Perl Home Page.
 
 If you believe you have an unreported bug, please run the L<perlbug> program
@@ -480,13 +270,13 @@ 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 see
-L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
-for details of how to report the issue.
+L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION> for details of how to
+report the issue.
 
 =head1 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 C<perlthanks> program:
+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 C<perlthanks> program:
 
     perlthanks