The perlsec passage to which you linked says the order shouldn't be assumed to be random. The perlrun passage to which you link doesn't explicitly mention changing key orderings at all. It is not the purpose of the feature to alter the key ordering, much less making it random.
Two problems with your assumption:
-
The feature in question only kicks in when needed.
-
Even if you could reliably trigger the feature, it's purpose is to salt the hashing algorithm (i.e. perturb bucket selection). While this has the side effect of affecting key ordering, it hasn't been shown to produce random key orderings.
But enough theory. Let's look at a practical example:
for (1..100) {
my %h;
$h{$_} = 1 for 'a'..'z';
print(join('', keys(%h)), "\n");
}
wraxdjyukhgftienvmslcpqbzo
wraxdjyukhgftienvmslpcqbzo
wraxdjyukhgftienvmslpcqbzo
wraxdjyukhgftienvmslpcqbzo
wraxdjyukhgftienvmslpcqbzo
wraxdjyukhgftienvmslpcqbzo
...
wraxdjyukhgftienvmslpcqbzo
wraxdjyukhgftienvmslpcqbzo
And the same if I run the program again.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|