In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/66056247dd2c721175d33eaf15386969664425ea?hp=ea88c40cb048cd70b799735e08ac60eb7e0cd54c>

- Log -----------------------------------------------------------------
commit 66056247dd2c721175d33eaf15386969664425ea
Author: Father Chrysostomos <spr...@cpan.org>
Date:   Mon Jan 16 23:12:12 2012 -0800

    perldelta: Typos and calrifications
-----------------------------------------------------------------------

Summary of changes:
 pod/perldelta.pod |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 0ea37d4..477ba85 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -502,7 +502,7 @@ has become this:
 
 =item *
 
-Some error message consist of multiple lines that are listed as separate
+Some error messages consist of multiple lines that are listed as separate
 entries in L<perldiag>.  splain has been taught to find the separate
 entries in these cases, instead of simply failing to find the message.
 
@@ -692,8 +692,8 @@ message.
 
 When one writes C<open foo || die>, which used to work in Perl 4, a
 "Precedence problem" warning is produced.  This warning used erroneously to
-apply to fully-qualified bareword handle names as well.  This has been
-corrected.
+apply to fully-qualified bareword handle names not followed by C<||>.  This
+has been corrected.
 
 =item * C<select> and package aliasing
 
@@ -761,7 +761,7 @@ more.
 =item * Unrecognised switches on C<#!> line
 
 If a switch, such as B<-x>, that cannot occur on the C<#!> line is used
-there, perl dies with "Can’t emulate...".
+there, perl dies with "Can't emulate...".
 
 It used to produce the same message for switches that perl did not
 recognise at all, whether on the command line or the C<#!> line.
@@ -782,7 +782,7 @@ Now it always updates those caches.
 =item * Hash element deletion and destructors
 
 When hash elements are deleted in void context, the internal hash entry is
-now freed before the value is freed, to prevent destructors call by that
+now freed before the value is freed, to prevent destructors called by that
 latter freeing from seeing the hash in an inconsistent state.  It was
 possible to cause double-frees if the destructor freed the hash itself
 [perl #100340].
@@ -866,7 +866,7 @@ The C<+=> operator does not usually warn when the left-hand 
side is
 C<undef>, but it was doing so for tied variables.  This has been fixed
 [perl #44895].
 
-=item * Tying and Autovivification
+=item * Tying and autovivification
 
 When Perl autovivifies an element of a tied array or hash (which entails
 calling STORE with a new reference), it now calls FETCH immediately after

--
Perl5 Master Repository

Reply via email to