Re^2: Truly randomized keys() in perl 5.17

Another possibility for your particular case is to sort keys. Performance penalty is small, and having random URLs generated each time is a bigger problem and can cause some caching issue and other troubles.

Comment on Re^2: Truly randomized keys() in perl 5.17 - a challenge for testing?

Replies are listed 'Best First'.
Re^3: Truly randomized keys() in perl 5.17 - a challenge for testing? by saintmike (Vicar) on Sep 30, 2013 at 17:05 UTC
You don't know if the performance penalty is small, who said the function isn't going to be used to run a billion times a second? The mere thought of dealing with this by adding useless production code to fix a test problem I find very disturbing.	[reply]
Re^4: Truly randomized keys() in perl 5.17 - a challenge for testing? by vsespb (Chaplain) on Sep 30, 2013 at 17:08 UTC
In this my answer I am talking not about fixing test, but about adjusting your business-requirements. I don't see case when having program output to be URLs with random parameters ordering is good idea. Better normalized URLs.	[reply]