summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2004-07-06 09:52:45 +0000
committerNicholas Clark <nick@ccl4.org>2004-07-06 09:52:45 +0000
commit64395df623b0e2ce9fb14bdc7b44295fb432a3a9 (patch)
tree70acda0d836dfd15521200392dd3244b79dd7205
parentb729eb0e29888960037917ed4ae3fcd621fe5991 (diff)
downloadperl-64395df623b0e2ce9fb14bdc7b44295fb432a3a9.tar.gz
Improvements suggested by Jarkko
p4raw-id: //depot/maint-5.8/perl@23053
-rw-r--r--pod/perl585delta.pod14
1 files changed, 7 insertions, 7 deletions
diff --git a/pod/perl585delta.pod b/pod/perl585delta.pod
index 9c16ad4677..69ac704ed4 100644
--- a/pod/perl585delta.pod
+++ b/pod/perl585delta.pod
@@ -15,7 +15,7 @@ There are no changes incompatible with 5.8.4.
Perl's regular expression engine now contains support for matching on the
intersection of two Unicode character classes. You can also now refer to
-user defined character classes from within other user defined character
+user-defined character classes from within other user defined character
classes.
=head1 Modules and Pragmata
@@ -140,13 +140,13 @@ the result would omit the value $b. This is now fixed.
=item *
-The unnecessary assignment optimisation introduced in 5.8.4 could give spurious
-warnings. This has been fixed.
+The optimisation for unnecessary assignments introduced in 5.8.4 could give
+spurious warnings. This has been fixed.
=item *
Perl should now correctly detect and read BOM-marked and (BOMless) UTF-16
-scripts.
+scripts of either endianness.
=item *
@@ -155,7 +155,7 @@ cause warnings at interpreter destruction time. The known bug is now fixed.
=item *
-Several obscure bugs involving manipulating utf8 strings with C<substr> have
+Several obscure bugs involving manipulating Unicode strings with C<substr> have
been fixed.
=item *
@@ -168,8 +168,8 @@ consistent with Unix shells' globbing behaviour.
=item *
Thread creation time could vary wildly between identical runs. This was caused
-by poor hashing algorithm in the thread cloning routines, which has now been
-fixed.
+by a poor hashing algorithm in the thread cloning routines, which has now
+been fixed.
=back