From: Jarkko Hietaniemi Date: Mon, 28 Jul 2003 04:51:46 +0000 (+0000) Subject: Clarify the process a bit. X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=e267033d98cea5c48492831d4add33c9b7ccb0c0;p=p5sagit%2Fp5-mst-13.2.git Clarify the process a bit. p4raw-id: //depot/perl@20251 --- diff --git a/INSTALL b/INSTALL index e3652d2..4b20540 100644 --- a/INSTALL +++ b/INSTALL @@ -847,14 +847,16 @@ and web services, that process data originating from external sources. In Perl 5.8.1 a security feature was introduced to make it harder 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 +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. 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. +see L. Another option is to add +-DUSE_HASH_SEED_EXPLICIT to the compilation flags (for example by +using C), in which case +one has to explicitly set the PERL_HASH_SEED environment variable to +enable the security feature, or by adding -DNO_HASH_SEED to the compilation +flags to completely disable the randomisation feature. B, and the ordering has already changed several times during the lifetime of