In perl.git, the branch blead has been updated
<https://perl5.git.perl.org/perl.git/commitdiff/569dc10932121baed0e806ccb1a6669300390011?hp=e1578db3c63a83a995f36808c21a147ea25db234>
- Log -----------------------------------------------------------------
commit 569dc10932121baed0e806ccb1a6669300390011
Author: Steve Hay <steve.m....@googlemail.com>
Date: Thu Jul 19 14:21:35 2018 +0100
perldelta - Updates, tidy-ups and remove boilerplate
commit 80ebe57f7bd7f07d3ad1ff9604b2580b98579582
Author: Steve Hay <steve.m....@googlemail.com>
Date: Thu Jul 19 13:49:00 2018 +0100
Fix VC6 build following commit aa3c16bd70
commit c96bf7f63a63c3f01bab0af6cf6b800db95d22e5
Author: Steve Hay <steve.m....@googlemail.com>
Date: Thu Jul 19 13:38:22 2018 +0100
perldeprecation.pod - Fix a couple of nits
commit b0a362a22b8eaee61bb2329d41c49b7c432f0257
Author: Steve Hay <steve.m....@googlemail.com>
Date: Thu Jul 19 09:17:54 2018 +0100
perldelta - Changes since 5.29.0
-----------------------------------------------------------------------
Summary of changes:
pod/perldelta.pod | 380 ++++++++++++++----------------------------------
pod/perldeprecation.pod | 6 +-
utf8.c | 2 +-
3 files changed, 112 insertions(+), 276 deletions(-)
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 261c76b273..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,406 +12,245 @@ 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 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 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:
-
- 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 ]
-
=head2 Delimiters must now be graphemes
-See L<perldeprecation/Use of unassigned code point or non-standalone grapheme
for a delimiter.>
+See L<perldeprecation/Use of unassigned code point or non-standalone grapheme
+for a delimiter.>
-=head2 Some formerly deprecated uses of an unescaped left brace C<"{">
-in regular expression patterns are now illegal
+=head2 Some formerly deprecated uses of an unescaped left brace C<"{"> in
+regular expression patterns are now illegal
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>.
-
-=head1 Deprecations
-
-XXX Any deprecated features, syntax, modules etc. should be listed here.
-
-=head2 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 C<"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.
-
-=over
-
-=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 ]
+raised. See L<perldeprecation/Unescaped left braces in regular expressions>.
=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 *
-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.
+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
=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.)
-
-[ Within each section, list entries as an =item entry ]
-
-=head2 New Modules and Pragmata
-
-=over 4
-
-=item *
-
-XXX Remove this section if not applicable.
-
-=back
-
=head2 Updated Modules and Pragmata
=over 4
=item *
-L<XXX> has been upgraded from version A.xx to B.yy.
+L<bignum> has been upgraded from version 0.49 to 0.50.
-If there was something important to note about this change, include that here.
-
-=back
+=item *
-=head2 Removed Modules and Pragmata
-
-=over 4
+L<Compress::Raw::Bzip2> has been upgraded from version 2.074 to 2.081.
=item *
-XXX
-
-=back
+L<Compress::Raw::Zlib> has been upgraded from version 2.076 to 2.081.
-=head1 Documentation
+=item *
-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>.
+L<Config::Perl::V> has been upgraded from version 0.29 to 0.30.
-=head2 New Documentation
+=item *
-XXX Changes which create B<new> files in F<pod/> go here.
+L<DB_File> has been upgraded from version 1.840 to 1.842.
-=head3 L<XXX>
+=item *
-XXX Description of the purpose of the new file here
+L<Digest::SHA> has been upgraded from version 6.01 to 6.02.
-=head2 Changes to Existing Documentation
+=item *
-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<perl...@perl.org|mailto:perl...@perl.org>.
+L<experimental> has been upgraded from version 0.019 to 0.020.
-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.
+=item *
-Additionally, the following selected changes have been made:
+L<ExtUtils::Manifest> has been upgraded from version 1.70 to 1.71.
-=head3 L<XXX>
+=item *
-=over 4
+L<File::Temp> has been upgraded from version 0.2304 to 0.2308.
=item *
-XXX Description of the change here
+IO-Compress has been upgraded from version 2.074 to 2.081.
-=back
+=item *
-=head1 Diagnostics
+L<IPC::Cmd> has been upgraded from version 1.00 to 1.02.
-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>.
+=item *
-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.
+L<Locale::Codes> has been upgraded from version 3.56 to 3.57.
-=head2 New Diagnostics
+=item *
-XXX Newly added diagnostic messages go under here, separated into New Errors
-and New Warnings
+L<Math::BigInt> has been upgraded from version 1.999811 to 1.999813.
-=head3 New Errors
+=item *
-=over 4
+L<Math::BigInt::FastCalc> has been upgraded from version 0.5006 to 0.5007.
=item *
-XXX L<message|perldiag/"message">
-
-=back
+L<Math::BigRat> has been upgraded from version 0.2613 to 0.2614.
-=head3 New Warnings
+=item *
-=over 4
+L<parent> has been upgraded from version 0.236 to 0.237.
=item *
-XXX L<message|perldiag/"message">
+L<perlfaq> has been upgraded from version 5.021011 to 5.20180605.
-=back
+=item *
-=head2 Changes to Existing Diagnostics
+podlators has been upgraded from version 4.10 to 4.11.
-XXX Changes (i.e. rewording) of diagnostic messages go here
+=item *
-=over 4
+L<Test::Simple> has been upgraded from version 1.302133 to 1.302138.
=item *
-XXX Describe change here
-
-=back
+L<Thread::Queue> has been upgraded from version 3.12 to 3.13.
-=head1 Utility Changes
+=item *
-XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
-Most of these are built within the directory F<utils>.
+L<Time::Local> has been upgraded from version 1.25 to 1.28.
-[ 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<version> has been upgraded from version 0.9923 to 0.9924.
-=over 4
+If there was something important to note about this change, include that here.
-=item *
+=back
-XXX
+=head1 Documentation
-=back
+=head2 Changes to Existing Documentation
-=head1 Configuration and Compilation
+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<perl...@perl.org|mailto:perl...@perl.org>.
-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.
+Additionally, the following selected changes have been made:
-[ List changes as an =item entry ].
+=head3 L<perlapi>
=over 4
=item *
-XXX
+C<AvFILL()> was wrongly listed as deprecated. This has been corrected.
+L<[perl #133278]|https://rt.perl.org/Ticket/Display.html?id=133278>
=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 ]
+=head3 L<perlop>
=over 4
=item *
-XXX
+The behaviour of C<tr> when the delimiter is an apostrophe has been clarified.
+In particular, hyphens aren't special, and C<\x{}> isn't interpolated.
+L<[perl #130679]|https://rt.perl.org/Ticket/Display.html?id=130679>
=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. ]
+=head1 Diagnostics
-=head2 New Platforms
+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 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.
+=head2 Changes to Existing Diagnostics
=over 4
-=item XXX-some-platform
+=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
-=head2 Discontinued Platforms
-
-XXX List any platforms that this version of perl no longer compiles on.
-
-=over 4
-
-=item XXX-some-platform
+=head1 Testing
-XXX
+Tests were added and changed to reflect the other additions and changes in this
+release.
-=back
+=head1 Platform Support
=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
+=item HP-UX 11.11
-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.
+An obscure problem in C<pack()> when compiling with HP C-ANSI-C has been fixed
+by disabling optimizations in F<pp_pack.c>.
-[ List each change as an =item entry ]
+=item Windows
=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
+The C<USE_CPLUSPLUS> build option which has long been available in
+F<win32/Makefile> (for B<nmake>) and F<win32/makefile.mk> (for B<dmake>) is now
+also available in F<win32/GNUmakefile> (for B<gmake>).
=item *
-XXX
+The B<nmake> makefile no longer defaults to Visual C++ 6.0 (a very old version
+which is unlikely to be widely used today). As a result, it is now a
+requirement to specify the C<CCTYPE> since there is no obvious choice of which
+modern version to default to instead. Failure to specify C<CCTYPE> will result
+in an error being output and the build will stop.
-=back
+(The B<dmake> and B<gmake> makefiles will automatically detect which compiler
+is being used, so do not require C<CCTYPE> to be set. This feature has not yet
+been added to the B<nmake> makefile.)
-=head1 Known Problems
+=back
-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.
+=back
-[ List each fix as an =item entry ]
+=head1 Selected Bug Fixes
=over 4
=item *
-XXX
-
-=back
-
-=head1 Errata From Previous Releases
-
-=over 4
+Compilation under C<-DPERL_MEM_LOG> and C<-DNO_LOCALE> have been fixed.
=item *
-XXX Add anything here that we forgot to add, or were mistaken about, in
-the perldelta of a previous release.
+Perl 5.28 introduced an C<index()> optimization when comparing to -1 (or
+indirectly, e.g. >= 0). When this optimization was triggered inside a C<when>
+clause it caused a warning ("Argument %s isn't numeric in smart match"). This
+has now been fixed.
+L<[perl #133368]|https://rt.perl.org/Ticket/Display.html?id=133368>
=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:
@@ -423,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
@@ -434,13 +270,13 @@ will be sent off to perl...@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
diff --git a/pod/perldeprecation.pod b/pod/perldeprecation.pod
index 211fb3c2b6..938d67832d 100644
--- a/pod/perldeprecation.pod
+++ b/pod/perldeprecation.pod
@@ -108,7 +108,7 @@ Literal uses of C<{> were deprecated in Perl 5.20, and some
uses of it
started to give deprecation warnings since. These cases were made fatal
in Perl 5.26. Due to an oversight, not all cases of a use of a literal
C<{> got a deprecation warning. Some cases started warning in Perl 5.26,
-and were made fatal in Perl 5.30. Other case started in Perl 5.28,
+and were made fatal in Perl 5.30. Other cases started in Perl 5.28,
and will be made fatal in 5.32.
=head2 Perl 5.30
@@ -239,13 +239,13 @@ As of Perl 5.30, use of delimiters which are
non-standalone graphemes is
fatal, in order to move the language to be able to accept
multi-character graphemes as delimiters.
-Also, as of Perl 5.30, delimiters which which are unassigned code points
+Also, as of Perl 5.30, delimiters which are unassigned code points
but that may someday become assigned are prohibited. Otherwise, code
that works today would fail to compile if the currently unassigned
delimiter ends up being something that isn't a stand-alone grapheme.
Because Unicode is never going to assign L<non-character code
points|perlunicode/Noncharacter code points>, nor L<code points that are
-above the legal Unicode maximum| perlunicode/Beyond Unicode code
+above the legal Unicode maximum|perlunicode/Beyond Unicode code
points>, those can be delimiters.
=head3 In XS code, use of various macros dealing with UTF-8.
diff --git a/utf8.c b/utf8.c
index 51039aed4f..57eac2d8f2 100644
--- a/utf8.c
+++ b/utf8.c
@@ -6363,7 +6363,7 @@ Perl_utf8_to_uvchr(pTHX_ const U8 *s, STRLEN *retlen)
}
return utf8_to_uvchr_buf(s,
- s + strnlen((char *) s, UTF8_MAXBYTES),
+ s + my_strnlen((char *) s, UTF8_MAXBYTES),
retlen);
}
--
Perl5 Master Repository
