From 0da9506150f50391997a25313a0b16f3d5860381 Mon Sep 17 00:00:00 2001 From: Florian Ragwitz Date: Wed, 19 Sep 2012 20:13:17 -0400 Subject: [PATCH] Fix a few perldelta nits --- pod/perldelta.pod | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pod/perldelta.pod b/pod/perldelta.pod index bfb3357..52eaf8f 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -315,7 +315,7 @@ length scalars being passed in. =item * -L has been upgraded from version 2.38 to 2.39. This contains Various +L has been upgraded from version 2.38 to 2.39. This contains various bugfixes, including compatibility fixes for older versions of Perl and vstring handling. @@ -516,7 +516,7 @@ The APIs for accessing lexical pads have changed considerably. Cs are now longer Cs, but their own type instead. Cs now contain a C and a C of Cs, rather than Cs for the pad and the list of pad names. Cs, Cs, and Cs are to -be accessed as such though the newly added pad API instead of the plain C +be accessed as such through the newly added pad API instead of the plain C and C APIs. See L for details. =item * @@ -595,7 +595,7 @@ omitted. =item * Reset the utf8 position cache when accessing magical variables to avoid the -string buffer and the utf8 position cache to get out of sync +string buffer and the utf8 position cache getting out of sync [perl #114410]. =item * @@ -627,7 +627,7 @@ but now is merely a warning (and that something won't match). [perl #82954]. =item * It used to be possible for formats defined in subroutines that have -subquently been undefined and redefined to close over variables in the +subsequently been undefined and redefined to close over variables in the wrong pad (the newly-defined enclosing sub), resulting in crashes or "Bizarre copy" errors. -- 2.7.4