|We don't bite newbies here... much|
Re^2: Hash orderingby davido (Cardinal)
|on Apr 14, 2020 at 22:07 UTC||Need Help??|
One nuance that AnomalousMonk is aware of but I wanted to clarify:
Let's say you start with a hash that looks like this:
The line of code above would capture only the keys (as was mentioned) and would save them only into the hash, so after running that line you would have this:
This is because the output of keys will just be foo, bazz, ping, putt, and when you take a flat list like that and store it into a hash, it is interpreted as key/value pairs. So your new hash loses all the values, and makes value out of half of the keys. If there are an odd number of keys, one of the new keys gets undef as its value, too.
If we were to break the assignment down to steps it would look more like this:
The sorting, itself is irrelevant because storing things in a hash loses any concept of order.