Martin DeMello wrote:
> Personally, I would love to see floats prohibited as hash keys, with
> the effect rippling outwards so that composite objects containing
> floats weren't valid hash keys either unless you overrode their hash
> method. I know the philosophy of ruby is to give users the power to
> shoot themselves in the foot, but as you say, people who know what
> they're doing won't use it anyway, and people who don't know about the
> pitfalls involved would appreciate the safeguard. If you are even
> vaguely contemplating this change, isn't now a good time to do it?

By composite objects, you mean arrays, rather than instances of 
user-defined classes or hashes, right? The latter hash by object id, not 
by contents, IIRC.

-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407