Stephen P Potter <[EMAIL PROTECTED]> writes: > What stops us from imposing order on this chaos? If they are currently > defined as not having any specific order, why can't we say they always > return in numeric || alphabetic || ASCII || whatever order we want? Because the fewer guarantees you make, the more efficiency you can get. The above would prevent a hypothetical future smart Perl interpretor from reordering your hash behind the scenes in another thread while your program is using it to optimize for the usage pattern that it's seeing, for example. If you have to guarantee a sorted traversal of the hash keys, your choices of data structures are *far* more limited. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
- Re: RFC 84 (v1) Replace => (stringifyi... Nathan Torkington
- Re: RFC 84 (v1) Replace => (string... John Porter
- Re: RFC 84 (v1) Replace => (string... Jonathan Scott Duff
- Re: RFC 84 (v1) Replace => (stringifying c... Stephen P. Potter
- Re: RFC 84 (v1) Replace => (stringifyi... Nathan Torkington
- Re: RFC 84 (v1) Replace => (string... Kai Henningsen
- Re: RFC 84 (v1) Replace => (stringifyi... Damien Neil
- Re: RFC 84 (v1) Replace => (string... Russ Allbery
- Re: RFC 84 (v1) Replace => (string... Stephen P. Potter
- Re: RFC 84 (v1) Replace => (string... Ariel Scolnicov
- Re: RFC 84 (v1) Replace => (string... Russ Allbery
- Re: RFC 84 (v1) Replace => (string... Uri Guttman
- Re: RFC 84 (v1) Replace => (stringifyi... Dan Sugalski
- Re: RFC 84 (v1) Replace => (stringifyi... John Porter
- Re: RFC 84 (v1) Replace => (stringifying comma) wit... Jeremy Howard
- Re: RFC 84 (v1) Replace => (stringifying comma... Jarkko Hietaniemi
- Array storage (was Re: RFC 84 (v1) Replace =&... Jeremy Howard
- Re: Array storage (was Re: RFC 84 (v1) Re... Jarkko Hietaniemi
- Re: Array storage (was Re: RFC 84 (v1... Dan Sugalski
- Re: Array storage (was Re: RFC 84 (v1... Jeremy Howard
- Re: Array storage (was Re: RFC 84 (v1) Re... Stephen P. Potter