in reply to Re^8: Get the order of HTTP request headers
in thread Get the order of HTTP request headers

Without a doubt, the order of the values returned by keys(%ENV) is unpredictable.

I really don't want to continue this, but just out of curiosity: How do you call a random number generator?

  • Comment on Re^9: Get the order of HTTP request headers

Replies are listed 'Best First'.
Re^10: Get the order of HTTP request headers
by ikegami (Patriarch) on May 06, 2010 at 21:22 UTC
    $a[rand(@a)], usually. Is that what you mean? I don't understand the question.
[reply]
[d/l]

      I meant "denote". But this is getting us nowhere. Your statement ...

      There's definitely no attempt to make them random

      ... is simply wrong and you just won't admit that, will you?

      But there is indeed a built-in hash randomization mechanism that is based on the same principle as the RNG in your favorite OS. And this mechanism is clearly documented in perlsec and perlrun.

      If you follow those links you will even find the phrases "randomise", "hash randomization" and "random perturbation".

      I don't know what else to say.

[reply]

        But there is indeed a built-in hash randomization mechanism

        We're talking about key orderings. It doesn't matter to this conversation whether bucket selection is random or not.

        And this mechanism is clearly documented in perlsec and perlrun.

        I've already refuted that. In fact, perlsec says exactly what I said: Also note that while the order of the hash elements might be randomised, this "pseudoordering" should not be used for applications like shuffling a list randomly.

        As for perlrun, the 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.

[reply]

In Section Seekers of Perl Wisdom