From b90ada5a1675d8de9e79ad2a4437d0678a700f67 Mon Sep 17 00:00:00 2001
From: Jarkko Hietaniemi <jhi@iki.fi>
Date: Fri, 11 Jul 2003 00:13:11 +0000
Subject: More retraction.

p4raw-id: //depot/perl@20138
---
 INSTALL | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

(limited to 'INSTALL')

diff --git a/INSTALL b/INSTALL
index e9cd2a6919..359c68af0a 100644
--- a/INSTALL
+++ b/INSTALL
@@ -849,12 +849,12 @@ to create such degenerate hashes.
 
 Because of this feature the keys(), values(), and each() functions
 may return the hash elements in different order between different
-runs of Perl even with the same data.  One can still revert to the old
-repeatable order by setting the environment variable PERL_HASH_SEED,
-see L<perlrun>.  Another option is to add -DUSE_HASH_SEED_EXPLICIT to
-the compilation flags, in which case one has to explicitly set the
-PERL_HASH_SEED environment variable to enable the security feature,
-or -DNO_HASH_SEED to completely disable the feature.
+runs of Perl even with the same data.  The additional randomisation
+is enabled if the environment variable PERL_HASH_SEED is set, see
+perlrun for details.
+
+One make the randomisation default by adding -DUSE_HASH_SEED to the
+compilation flags, or completely disable it by adding -DNO_HASH_SEED.
 
 B<Perl has never guaranteed any ordering of the hash keys>, and the
 ordering has already changed several times during the lifetime of
-- 
cgit v1.2.1