X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlsec.pod;h=41f96691aca4905d665c752766fa6d87f27ebaed;hb=593b9c1462e1fc8a2425e215f64b2197e1bfb796;hp=92853dde1ca8c3673649297d1fd9d450784cd51e;hpb=504f80c1f3625809f472c1ce21089fdae860d9fd;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlsec.pod b/pod/perlsec.pod index 92853dd..41f9669 100644 --- a/pod/perlsec.pod +++ b/pod/perlsec.pod @@ -417,6 +417,19 @@ consecutive runs of Perl will order hash keys differently, which may confuse some applications (like Data::Dumper: the outputs of two different runs are no more identical). +B, and the +ordering has already changed several times during the lifetime of +Perl 5. Also, the ordering of hash keys has always been, and +continues to be, affected by the insertion order. + +Also note that while the order of the hash elements might be +randomised, this "pseudoordering" should B be used for +applications like shuffling a list randomly (use List::Util::shuffle() +for that, see L, a standard core module since Perl 5.8.0; +or the CPAN module Algorithm::Numerical::Shuffle), or for generating +permutations (use e.g. the CPAN modules Algorithm::Permute or +Algorithm::FastPermute), or for any cryptographic applications. + =item * Regular expressions - Perl's regular expression engine is so called