Change 19933 by [EMAIL PROTECTED] on 2003/07/02 14:55:49
Subject: Re: maint @ 19923
From: Ronald J Kimball <[EMAIL PROTECTED]>
Date: Wed, 2 Jul 2003 11:43:05 -0400
Message-ID: <[EMAIL PROTECTED]>
Affected files ...
... //depot/perl/pod/perlfunc.pod#393 edit
Differences ...
==== //depot/perl/pod/perlfunc.pod#393 (text) ====
Index: perl/pod/perlfunc.pod
--- perl/pod/perlfunc.pod#392~19932~ Wed Jul 2 07:29:42 2003
+++ perl/pod/perlfunc.pod Wed Jul 2 07:55:49 2003
@@ -1271,8 +1271,7 @@
guaranteed to be in the same order as either the C<keys> or C<values>
function would produce on the same (unmodified) hash. Since Perl
5.8.1 the ordering is different even between different runs of Perl
-because of security reasons (see L<perlsec/"Algorithmic Complexity
-Attacks">)
+for security reasons (see L<perlsec/"Algorithmic Complexity Attacks">).
When the hash is entirely read, a null array is returned in list context
(which when assigned produces a false (C<0>) value), and C<undef> in
@@ -2320,10 +2319,10 @@
The keys are returned in an apparently random order. The actual
random order is subject to change in future versions of perl, but it
is guaranteed to be the same order as either the C<values> or C<each>
-function produces (given that the hash has not been modified).
-Since Perl 5.8.1 the ordering is different even between different
-runs of Perl because of security reasons (see L<perlsec/"Algorithmic
-Complexity Attacks">)
+function produces (given that the hash has not been modified). Since
+Perl 5.8.1 the ordering is different even between different runs of
+Perl for security reasons (see L<perlsec/"Algorithmic Complexity
+Attacks">).
As a side effect, calling keys() resets the HASH's internal iterator,
see L</each>.
@@ -6222,8 +6221,7 @@
is guaranteed to be the same order as either the C<keys> or C<each>
function would produce on the same (unmodified) hash. Since Perl
5.8.1 the ordering is different even between different runs of Perl
-because of security reasons (see L<perlsec/"Algorithmic Complexity
-Attacks">)
+for security reasons (see L<perlsec/"Algorithmic Complexity Attacks">).
As a side effect, calling values() resets the HASH's internal iterator,
see L</each>.
End of Patch.
