In perl.git, the branch maint-5.20 has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/0e01dafe73b545efb8ad973a2350ff80abedb4d4?hp=f659636a49dd034a887cd31111d0379455dfbc95>

- Log -----------------------------------------------------------------
commit 0e01dafe73b545efb8ad973a2350ff80abedb4d4
Author: Steve Hay <[email protected]>
Date:   Thu Jan 29 08:51:26 2015 +0000

    perldelta - Copy-editing

M       pod/perldelta.pod

commit b14dbf06ac806fca2d8297a7774515f5d0d1fa90
Author: Steve Hay <[email protected]>
Date:   Thu Jan 29 08:43:34 2015 +0000

    perldelta - Two spelling corrections

M       pod/perldelta.pod

commit 15cb46fc8f9cca5948db49897109f434d1627422
Author: Steve Hay <[email protected]>
Date:   Thu Jan 29 08:36:35 2015 +0000

    perldelta - Remove boilerplate sections except for Acknowledgements

M       pod/perldelta.pod

commit adb84517248c45bf01afef7bbdb01af4ad430a2f
Author: Steve Hay <[email protected]>
Date:   Thu Jan 29 08:32:17 2015 +0000

    perldelta - Note the addition of perlunicook
    
    Manually backported from commit 9ce6583ecf6a46b2c441882c4eb964964e787e74.

M       pod/perldelta.pod
-----------------------------------------------------------------------

Summary of changes:
 pod/perldelta.pod | 228 +++++++++++-------------------------------------------
 1 file changed, 44 insertions(+), 184 deletions(-)

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 3d3c436..d617b55 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.20.2
 
 =head1 DESCRIPTION
@@ -15,39 +12,12 @@ release.
 If you are upgrading from an earlier release such as 5.20.0, first read
 L<perl5201delta>, which describes differences between 5.20.0 and 5.20.1.
 
-=head1 Notice
-
-XXX Any important notices here
-
-=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
 
 There are no changes intentionally incompatible with 5.20.1.  If any exist,
 they are bugs, and we request that you submit a report.  See L</Reporting Bugs>
 below.
 
-=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 a =item entry ]
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
 =head1 Modules and Pragmata
 
 =head2 Updated Modules and Pragmata
@@ -100,15 +70,15 @@ A warning from the B<gcc> compiler is now avoided when 
building the XS.
 
 L<PerlIO::scalar> has been upgraded from version 0.18 to 0.18_01.
 
-Reading from a position well past the end of the scalar now correctly
-returns end of file.
+Reading from a position well past the end of the scalar now correctly returns
+end of file.
 L<[perl #123443]|https://rt.perl.org/Ticket/Display.html?id=123443>
 
-Seeking to a negative position still fails, but no longer leaves the
-file position set to a negation location.
+Seeking to a negative position still fails, but no longer leaves the file
+position set to a negation location.
 
-C<eof()> on a C<PerlIO::scalar> handle now properly returns true when
-the file position is past the 2GB mark on 32-bit systems.
+C<eof()> on a C<PerlIO::scalar> handle now properly returns true when the file
+position is past the 2GB mark on 32-bit systems.
 
 =item *
 
@@ -120,23 +90,15 @@ Minor grammatical change to the documentation only.
 
 =head1 Documentation
 
-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>
+=head3 L<perlunicook>
 
-XXX Description of the purpose of the new file here
+This document, by Tom Christiansen, provides examples of handling Unicode in
+Perl.
 
 =head2 Changes to Existing Documentation
 
-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.
-
 =head3 L<perlexperiment>
 
 =over 4
@@ -177,13 +139,8 @@ 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 Changes to Existing Diagnostics
 
-XXX Changes (i.e. rewording) of diagnostic messages go here
-
 =over 4
 
 =item *
@@ -198,52 +155,8 @@ documented.  This warning is not new, but was not 
previously documented 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 directories F<utils> and F<x2p>.
-
-[ 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 a =item entry ].
-
-=over 4
-
-=item *
-
-XXX
-
-=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.
-
-[ List each test improvement as a =item entry ]
-
 =over 4
 
 =item *
@@ -256,54 +169,13 @@ fixed.
 
 =head1 Platform Support
 
-XXX Any changes to platform support should be listed in the sections below.
-
-[ Within the sections, list each platform as a =item entry with specific
-changes as paragraphs below it. ]
-
 =head2 Regained Platforms
 
-IRIX and Tru64 platforms are working again.
-(Some C<make test> failures remain.)
-
-=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 a =item entry ]
-
-=over 4
-
-=item *
-
-XXX
-
-=back
+IRIX and Tru64 platforms are working again.  (Some C<make test> failures
+remain.)
 
 =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 a =item entry ]
-
 =over 4
 
 =item *
@@ -315,8 +187,8 @@ L<[cpan 
#85570]|https://rt.cpan.org/Ticket/Display.html?id=85570>
 
 =item *
 
-In Perl 5.20.0, C<$^N> accidentally had the internal UTF8 flag turned off
-if accessed from a code block within a regular expression, effectively
+In Perl 5.20.0, C<$^N> accidentally had the internal UTF8 flag turned off if
+accessed from a code block within a regular expression, effectively
 UTF8-encoding the value.  This has been fixed.
 L<[perl #123135]|https://rt.perl.org/Ticket/Display.html?id=123135>
 
@@ -341,24 +213,23 @@ L<[perl 
#122747]|https://rt.perl.org/Ticket/Display.html?id=122747>
 =item *
 
 Due to a mistake in the string-copying logic, copying the value of a state
-variable could instead steal the value and undefine the variable.  This
-bug, introduced in 5.20, would happen mostly for long strings (1250 chars
-or more), but could happen for any strings under builds with copy-on-write
+variable could instead steal the value and undefine the variable.  This bug,
+introduced in Perl 5.20, would happen mostly for long strings (1250 chars or
+more), but could happen for any strings under builds with copy-on-write
 disabled.
 L<[perl #123029]|https://rt.perl.org/Ticket/Display.html?id=123029>
 
 =item *
 
-Fixed a bug that could cause perl to execute an infite loop during
+Fixed a bug that could cause perl to execute an infinite loop during
 compilation.
 L<[perl #122995]|https://rt.perl.org/Ticket/Display.html?id=122995>
 
 =item *
 
-On Win32, restoring in a child pseudo-process a variable that was
-C<local()>ed in a parent pseudo-process before the C<fork> happened caused
-memory corruption and a crash in the child pseudo-process (and therefore OS
-process).
+On Win32, restoring in a child pseudo-process a variable that was C<local()>ed
+in a parent pseudo-process before the C<fork> happened caused memory corruption
+and a crash in the child pseudo-process (and therefore OS process).
 L<[perl #40565]|https://rt.perl.org/Ticket/Display.html?id=40565>
 
 =item *
@@ -369,26 +240,26 @@ L<[perl 
#122669]|https://rt.perl.org/Ticket/Display.html?id=122669>
 
 =item *
 
-Calling C<write> on a format with a C<^**> field could produce a panic
-in sv_chop() if there were insufficient arguments or if the variable
-used to fill the field was empty.
+Calling C<write> on a format with a C<^**> field could produce a panic in
+sv_chop() if there were insufficient arguments or if the variable used to fill
+the field was empty.
 L<[perl #123245]|https://rt.perl.org/Ticket/Display.html?id=123245>
 
 =item *
 
-In perl 5.20.0, C<sort CORE::fake> where 'fake' is anything other than a
-keyword started chopping of the last 6 characters and treating the result
-as a sort sub name.  The previous behaviour of treating "CORE::fake" as a
-sort sub name has been restored.
+In Perl 5.20.0, C<sort CORE::fake> where 'fake' is anything other than a
+keyword started chopping of the last 6 characters and treating the result as a
+sort sub name.  The previous behaviour of treating "CORE::fake" as a sort sub
+name has been restored.
 L<[perl #123410]|https://rt.perl.org/Ticket/Display.html?id=123410>
 
 =item *
 
-A bug in regular expression patterns that could lead to segfaults and
-other crashes has been fixed.  This occurred only in patterns compiled
-with C<"/i">, while taking into account the current POSIX locale (this usually
-means they have to be compiled within the scope of C<S<"use locale">>),
-and there must be a string of at least 128 consecutive bytes to match.
+A bug in regular expression patterns that could lead to segfaults and other
+crashes has been fixed.  This occurred only in patterns compiled with C<"/i">,
+while taking into account the current POSIX locale (this usually means they
+have to be compiled within the scope of C<S<"use locale">>), and there must be
+a string of at least 128 consecutive bytes to match.
 L<[perl #123539]|https://rt.perl.org/Ticket/Display.html?id=123539>
 
 =item *
@@ -404,8 +275,8 @@ L<[perl 
#123495]|https://rt.perl.org/Ticket/Display.html?id=123495>
 =item *
 
 Certain syntax errors in substitutions, such as C<< s/${<>{})// >>, would
-crash, and had done so since Perl 5.10.  (In some cases the crash did not
-start happening till 5.16.)  The crash has, of course, been fixed.
+crash, and had done so since Perl 5.10.  (In some cases the crash did not start
+happening until Perl 5.16.)  The crash has, of course, been fixed.
 L<[perl #123542]|https://rt.perl.org/Ticket/Display.html?id=123542>
 
 =item *
@@ -416,10 +287,10 @@ L<[perl 
#123198]|https://rt.perl.org/Ticket/Display.html?id=123198>
 
 =item *
 
-C<< formline("@...", "a"); >> would crash.  The C<FF_CHECKNL> cas in
-pp_formline() didn't set the pointer used to mark the chop position,
-which led to the C<FF_MORE> case crashing with a segmentation fault.
-This has been fixed.
+C<< formline("@...", "a"); >> would crash.  The C<FF_CHECKNL> case in
+pp_formline() didn't set the pointer used to mark the chop position, which led
+to the C<FF_MORE> case crashing with a segmentation fault.  This has been
+fixed.
 L<[perl #123538]|https://rt.perl.org/Ticket/Display.html?id=123538>
 L<[perl #123622]|https://rt.perl.org/Ticket/Display.html?id=123622>
 
@@ -433,12 +304,6 @@ L<[perl 
#123604]|https://rt.perl.org/Ticket/Display.html?id=123604>
 
 =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 a =item entry ]
-
 =over 4
 
 =item *
@@ -454,19 +319,14 @@ argument to C<sort>.  This will be fixed in a future 
version of Perl.
 
 =item *
 
-A regression has been fixed that was introduced in v5.20.0 (fixed in
-v5.20.1 as well as here) in which a UTF-8 encoded regular expression
-pattern that contains a single ASCII lowercase letter does not match its
-uppercase counterpart.
+A regression has been fixed that was introduced in Perl 5.20.0 (fixed in Perl
+5.20.1 as well as here) in which a UTF-8 encoded regular expression pattern
+that contains a single ASCII lowercase letter does not match its uppercase
+counterpart.
 L<[perl #122655]|https://rt.perl.org/Ticket/Display.html?id=122655>
 
 =back
 
-=head1 Obituary
-
-XXX If any significant core contributor has died, we've added a short obituary
-here.
-
 =head1 Acknowledgements
 
 XXX Generate this with:
@@ -477,8 +337,8 @@ XXX Generate this with:
 
 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.
+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 L<perlbug> program
 included with your release.  Be sure to trim your bug down to a tiny but

--
Perl5 Master Repository

Reply via email to