some 589 delta nits

Message-ID: <493C1856.5030907@iki.fi>
Date: Sun, 07 Dec 2008 13:39:18 -0500

p4raw-id: //depot/maint-5.8/perl@35057

1 files changed, 30 insertions, 18 deletions

diff --git a/pod/perl589delta.pod b/pod/perl589delta.pod
index 0ef9b4e129..00a94f97d8 100644
--- a/pod/perl589delta.pod
+++ b/pod/perl589delta.pod
@@ -7,6 +7,14 @@ perldelta - what is new for perl v5.8.9
 This document describes differences between the 5.8.8 release and
 the 5.8.9 release.
 
+=head1 Notice
+
+The 5.8.9 will be the last significant release of the 5.8.x
+series. Any future releases of 5.8.x will likely only be to deal with
+security issues, and platform build failures. Hence you should look to
+migrating to 5.10.x, if you have not started already.
+See L</"Known Problems"> for more information.
+
 =head1 Incompatible Changes
 
 A particular construction in the source code of extensions written in C++
@@ -22,7 +30,7 @@ If any exist, they are bugs and reports are welcome.
 =head2 Unicode Character Database 5.1.0.
 
 The copy of the Unicode Character Database included in Perl 5.8 has
-been updated to 5.1.0 from 4.1.0 See
+been updated to 5.1.0 from 4.1.0. See
 L<http://www.unicode.org/versions/Unicode5.1.0/#NotableChanges> for the
 notable changes.
 
@@ -121,7 +129,8 @@ C<-Dv> displays the process id as part of the trace output.
 =head2 XS-assisted SWASHGET
 
 Some pure-perl code that the regexp engine was using to retrieve Unicode
-properties and transliteration mappings has been reimplemented in XS.
+properties and transliteration mappings has been reimplemented in XS
+for faster execution.
 (SADAHIRO Tomoyuki)
 
 =head2 Constant subroutines
@@ -370,7 +379,8 @@ C<blib> upgraded to 0.04
 
 C<Carp> upgraded to version 1.10
 
-The argument backtrace code would show C<undef> as I<"undef"> - a string.
+The argument backtrace code now shows C<undef> as C<undef>,
+instead of a string I<"undef">.
 
 =item *
 
@@ -1500,7 +1510,7 @@ Fixed bug RT #40641 - encoding of Unicode characters in regular expressions.
 Fixed a bug where using certain patterns in a regexp led to a panic.
 [RT #45337]
 
-Perl longer segfaults (due to infinite internal recursion) if the locale's
+Perl no longer segfaults (due to infinite internal recursion) if the locale's
 character is not UTF-8 [RT #41442]:
 
     use open ':locale';
@@ -1657,9 +1667,9 @@ underlying hash.
 
 =item *
 
-Fix bug RT #6006, regexp replaces using large replacement variables fail some of
-the time, I<i.e.> when substitution contains something like C<${10}> (note the
-bracket) instead of just C<$10>.
+Fix bug RT #6006, regexp replaces using large replacement variables
+fail some of the time, I<i.e.> when substitution contains something
+like C<${10}> (note the bracket) instead of just C<$10>.
 
 =item *
 
@@ -1965,9 +1975,9 @@ replacement of the common idiom
     sv = newSV(0);
     sv_upgrade(sv, type);
 
-Similarly C<Perl_newSVpvn_flags()> can be used to combine C<Perl_newSVpv()> with
-C<Perl_sv_2mortal()> or the equivalent C<Perl_sv_newmortal()> with
-C<Perl_sv_setpvn()>
+Similarly C<Perl_newSVpvn_flags()> can be used to combine
+C<Perl_newSVpv()> with C<Perl_sv_2mortal()> or the equivalent
+C<Perl_sv_newmortal()> with C<Perl_sv_setpvn()>
 
 Two new macros C<mPUSHs()> and C<mXPUSHs()> are added, to make it easier to
 push mortal SVs onto the stack. They were then used to fix several bugs where
@@ -2103,7 +2113,8 @@ Tests for C<subst> run under C<-T> mode.
 
 =item t/op/symbolcache.t
 
-Tests for C<undef> and C<delete> on stash entries that are bound to subroutines or methods.
+Tests for C<undef> and C<delete> on stash entries that are bound to
+subroutines or methods.
 
 =item t/op/upgrade.t
 
@@ -2156,13 +2167,14 @@ Also, many bug fixes present in 5.10.0 can't be back-ported to the 5.8.x
 branch, because they require changes that are binary incompatible, or because
 the code changes are too large and hence too risky to incorporate.
 
-We have only limited volunteer labour, and the maintenance burden is getting
-increasingly complex. Hence this will be the last significant release of the
-5.8.x series. Any future releases of 5.8.x will likely only be to deal with
-security issues, and platform build failures. Hence you should look to
-migrating to 5.10.x, if you have not started already. Alternatively, if business
-requirements constrain you to continue to use 5.8.x, you may wish to consider
-commercial support from firms such as ActiveState.
+We have only limited volunteer labour, and the maintenance burden is
+getting increasingly complex. Hence this will be the last significant
+release of the 5.8.x series. Any future releases of 5.8.x will likely
+only be to deal with security issues, and platform build
+failures. Hence you should look to migrating to 5.10.x, if you have
+not started already. Alternatively, if business requirements constrain
+you to continue to use 5.8.x, you may wish to consider commercial
+support from firms such as ActiveState.
 
 =head1 Platform Specific Notes