Change 19938 by [EMAIL PROTECTED] on 2003/07/02 20:07:12

        Subject: Perldelta 5.8.1 typos
        From: Simon Glover <[EMAIL PROTECTED]>
        Date: Wed, 2 Jul 2003 13:42:58 -0400 (EDT)
        Message-ID: <[EMAIL PROTECTED]>

Affected files ...

... //depot/maint-5.8/perl/pod/perldelta.pod#13 edit

Differences ...

==== //depot/maint-5.8/perl/pod/perldelta.pod#13 (text) ====
Index: perl/pod/perldelta.pod
--- perl/pod/perldelta.pod#12~19937~    Wed Jul  2 13:06:17 2003
+++ perl/pod/perldelta.pod      Wed Jul  2 13:07:12 2003
@@ -36,8 +36,8 @@
 or if some particular order is really important, use tied hashes.
 
 The hash randomisation is certain to reveal hidden assumptions about
-some particular ordering of hash elements, and outright bugs: it did
-reveal few bugs from the Perl core and core modules.
+some particular ordering of hash elements, and outright bugs: it
+revealed a few bugs in the Perl core and core modules.
 
 See L<perlsec/"Algorithmic Complexity Attacks"> for the rationale
 behind this change.
@@ -55,7 +55,7 @@
 =head2 UTF-8 no more default under UTF-8 locales
 
 In Perl 5.8.0 many Unicode features were introduced.   One of them
-was found the be more of nuisance than benefit: the automagic
+was found to be of more nuisance than benefit: the automagic
 (and silent) "UTF-8-ification" of filehandles, including the
 standard filehandles, if the user's locale settings indicated
 use of UTF-8.
@@ -443,7 +443,7 @@
 
 =head2 Win32 sysread, syswrite
 
-In Win32 the problem of sysread/syswritebecoming "broken" in 5.8.0 is
+In Win32 the problem of sysread/syswrite becoming "broken" in 5.8.0 is
 still open.  Background: before 5.8.0 in Win32 a filehandle that had
 been opened with sysopen() and then read/written with sysread/syswrite
 still did the CRLF <-> LF translation emblematic of Win32.
@@ -456,8 +456,8 @@
 This is still the case with 5.8.1 since the proper fix would require a
 considerable effort to implement cleanly, and secondly because one can
 argue that the old behaviour of sysread/syswrite on Win32 was simply
-anomalous (that is, wrong), since it makes Win32 to behave differently
-than any other platform.
+anomalous (that is, wrong), since it makes Win32 behave differently
+from any other platform.
 
 =head1 Reporting Bugs
 
End of Patch.

Reply via email to