diff options
author | Jarkko Hietaniemi <jhi@iki.fi> | 2003-07-11 00:13:11 +0000 |
---|---|---|
committer | Jarkko Hietaniemi <jhi@iki.fi> | 2003-07-11 00:13:11 +0000 |
commit | b90ada5a1675d8de9e79ad2a4437d0678a700f67 (patch) | |
tree | e769084e6b83b6d4257a865add95fe72da1fb07b /INSTALL | |
parent | f66d27219d38f673658dece7f9afd3498a458e6d (diff) | |
download | perl-b90ada5a1675d8de9e79ad2a4437d0678a700f67.tar.gz |
More retraction.
p4raw-id: //depot/perl@20138
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -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 |