<snip/>
Well CaseInsensitive as a name doesn't imply to me that it changes anything.
It implies that is compares insenstively (including equals, which should be
handled).
So two maps whose keys differ only on key case *are* equal?
This map would be a LowerCaseKeyMap or some such.
It strikes me that if I put a key in one way, I should get it back that way too.
I guess that is a valid point, though the cost of this will be to force every comparison to do something like toString().toLower().
<side comment>
BTW: the names now exclude 'Hash' as much as possible, hence it would be CaseInsensitiveMap
It is interesting to note that what is going on here is that a CaseInsensitiveMap is a map on equivalence classes of keys and the design question is whether to store canonical equivalence class representatives and use canonicalized access functions or to implement the equivalence relation internally. The advantage of the second approach is that you can recover the keys exactly as they have been entered, the disadvantage is that one-time canonicalization may be more efficient.
</side comment>
Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
