In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/7e3fee74f8eeb5f24e3d1b8f7ab2cd33305ecb31?hp=113f3f4c0cc6a922005edcdd0df9cba0a4285d49>

- Log -----------------------------------------------------------------
commit 7e3fee74f8eeb5f24e3d1b8f7ab2cd33305ecb31
Author: Ævar Arnfjörð Bjarmason <a...@cpan.org>
Date:   Sun Feb 20 14:49:28 2011 +0000

    pod/perldelta.pod: remove XXX entries
    
    Remove all the XXX entries in the template perldelta.pod. Also move
    the note about the perlbug change to the "Utility Changes" section,
    and uniformly turn "=item * $FOO" sections into "=item *\n\n$FOO"
    sections.
-----------------------------------------------------------------------

Summary of changes:
 pod/perldelta.pod |  245 ++++++-----------------------------------------------
 1 files changed, 27 insertions(+), 218 deletions(-)

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index a9ea7d3..b984667 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -2,32 +2,19 @@
 
 =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.13.10
 
 =head1 DESCRIPTION
 
-This document describes differences between the 5.XXX.XXX release and
-the 5.XXX.XXX release.
-
-If you are upgrading from an earlier release such as 5.YYY.YYY, first read
-L<perl5YYYdelta>, which describes differences between 5.ZZZ.ZZZ and
-5.YYY.YYY.
+This document describes differences between the 5.13.9 release and
+the 5.13.10 release.
 
-=head1 Notice
-
-XXX Any important notices here
+If you are upgrading from an earlier release such as 5.13.8, first read
+L<perl5139delta>, which describes differences between 5.13.8 and
+5.13.9.
 
 =head1 Core Enhancements
 
-XXX New core language features go here. Summarise 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 ]
-
 =head2 The new regular expression modifiers available in suffix form
 
 Various releases of the 5.13.x series have added new regular expression
@@ -73,21 +60,8 @@ maximum of 0x10FFFF are encountered.
 
 =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 reports are welcome.
-
-[ List each incompatible change as a =head2 entry ]
-
 =head2 Most C<\p{}> properties are now immune from case-insensitive matching
 
 For most Unicode properties, it doesn't make sense to have them match
@@ -112,13 +86,6 @@ C</i> must change to read the new boolean parameter passed 
it which is
 non-zero if case-insensitive matching is in effect; 0 if not.  See
 L<perluniprops/User-Defined Character Properties>.
 
-=head2 [perl #82996] Use the user's from address as return-path in perlbug
-
-Many systems these days don't have a valid Internet domain name and
-perl...@perl.org does not accept email with a return-path that does
-not resolve. Therefore pass the user's address to sendmail so it's
-less likely to get stuck in a mail queue somewhere. (019cfd2)
-
 =head2 regex: \p{} in pattern implies Unicode semantics
 
 Now, a Unicode property match specified in the pattern will indicate
@@ -204,35 +171,8 @@ It is planned to remove this feature in Perl 5.16.  A CPAN 
module
 providing improved functionality is being prepared for release by the
 time 5.14 is.
 
-[ List each 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 a =item entry ]
-
-=over 4
-
-=item *
-
-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>, which prints stub
-entries to STDOUT.  Results can be pasted in place of the '=head2' entries
-below.  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.
-
-[ Within each section, list entries as a =item entry ]
-
 =head2 New Modules and Pragmata
 
 =over 4
@@ -430,41 +370,12 @@ or of "Mathematical Bold" digits would would be safe.
 
 C<CPAN> has been upgraded from version1.94_63 to 1.94_64.
 
-=item *
-
-XXX
-
-=back
-
-=head2 Removed Modules and Pragmata
-
-=over 4
-
-=item *
-
-XXX
-
 =back
 
 =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>
-
-XXX Description of the purpose of the new file here
-
 =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<overload>
 
 =over 4
@@ -536,15 +447,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.
-
-[ Within each section, list entries as a =item entry ]
-
 =head2 New Diagnostics
 
-XXX Newly added diagnostic messages go here
-
 =over 4
 
 =item "\b{" is deprecated; use "\b\{" instead
@@ -574,8 +478,6 @@ pipe is about to be closed.
 
 =head2 Changes to Existing Diagnostics
 
-XXX Changes (i.e. rewording) of diagnostic messages go here
-
 =over 4
 
 =item *
@@ -585,50 +487,41 @@ changed to include any literal '{' following the 2-char 
escape.  e.g.,
 "\q{" will include the { in the message as part of the escape
 (216bfc0).
 
-=item * C<binmode $fh, ':scalar'> no longer warns (8250589)
+=item *
+
+C<binmode $fh, ':scalar'> no longer warns (8250589)
 
 Perl will now no longer produce this warning:
 
     $ perl -we 'open my $f, ">", \my $x; binmode $f, "scalar"'
     Use of uninitialized value in binmode at -e line 1.
 
-=item *
-
-XXX
-
 =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 =head3 entry for each utility and =item
-entries for each change
-Use L<XXX> with program names to get proper documentation linking. ]
-
-=head3 L<XXX>
+=head3 L<perlbug>
 
 =over 4
 
 =item *
 
-XXX
+[perl #82996] Use the user's from address as return-path in perlbug
+
+Many systems these days don't have a valid Internet domain name and
+perl...@perl.org does not accept email with a return-path that does
+not resolve. Therefore pass the user's address to sendmail so it's
+less likely to get stuck in a mail queue somewhere. (019cfd2)
 
 =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 * make reg_eval_scope.t TODOs consistently fail (daaf7ac)
+=item *
+
+make reg_eval_scope.t TODOs consistently fail (daaf7ac)
 
 Some of the TODO tests in reg_eval_scope.t spuriously passed under
 non-threaded builds. Make the tests harder so they always fail.
@@ -644,22 +537,10 @@ Stop EU::CBuilder's tests from failing in parallel 
(cbf59d5)
 It used to use the same paths for temporary files in all tests. This
 blew up randomly when the tests were run in parallel.
 
-=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 summarising, although the bugs
-that they represent may be covered elsewhere.
-
-[ List each test improvement as a =item entry ]
-
 =over 4
 
 =item *
@@ -676,45 +557,8 @@ extensions are built statically.
 
 =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 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 Windows
@@ -752,15 +596,11 @@ like in the other BSD dialects.
 
 =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 test improvement as a =item entry ]
-
 =over 4
 
-=item * Fix harmless invalid read in Perl_re_compile() (f6d9469)
+=item *
+
+Fix harmless invalid read in Perl_re_compile() (f6d9469)
 
 [perl #2460] described a case where electric fence reported an invalid
 read. This could be reproduced under valgrind with blead and -e'/x/',
@@ -775,7 +615,9 @@ long enough to spill into the type field of the "next node".
 Fix this by only using NEXTOPER(first) when we know the first node is
 kosher.
 
-=item * Break out the generated function Perl_keywords() into F<keywords.c>, a 
new file. (26ea9e1)
+=item *
+
+Break out the generated function Perl_keywords() into F<keywords.c>, a new 
file. (26ea9e1)
 
 As it and Perl_yylex() both need FEATURE_IS_ENABLED, feature_is_enabled() is
 no longer static, and the two macro definitions move from toke.c to perl.h
@@ -788,7 +630,9 @@ middle of toke.c, and it was not clear that it was 
generated code.
 A lot of tests have been ported from Test to Test::More, e.g. in
 3842ad6.
 
-=item * Increase default PerlIO buffer size. (b83080d)
+=item *
+
+Increase default PerlIO buffer size. (b83080d)
 
 The previous default size of a PerlIO buffer (4096 bytes) has been increased
 to the larger of 8192 bytes and your local BUFSIZ.  Benchmarks show that 
doubling
@@ -802,21 +646,10 @@ larger value, configure with:
 where N is the desired size in bytes; it should probably be a multiple of
 your page size.
 
-
-=item *
-
-XXX
-
 =back
 
 =head1 Selected Bug Fixes
 
-XXX Important bug fixes in the core language are summarised here.
-Bug fixes in files in F<ext/> and F<lib/> are best summarised in
-L</Modules and Pragmata>.
-
-[ List each fix as a =item entry ]
-
 =over 4
 
 =item *
@@ -930,30 +763,6 @@ point it is.
 
 =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, unless
-they were specific to a particular platform (see below).
-
-This is a list of some significant unfixed bugs, which are regressions
-from either 5.XXX.XXX or 5.XXX.XXX.
-
-[ List each fix as a =item entry ]
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head1 Obituary
-
-XXX If any significant core contributor has died, we've added a short obituary
-here.
-
 =head1 Acknowledgements
 
 XXX The list of people to thank goes here.

--
Perl5 Master Repository

Reply via email to