> I will say that it is quite nice that after the refactoring, things like 
> the SqueakMap package loader now use case insensitive sorting.  I guess 
> I had gotten used to the default case-sensitive sorting in these types 
> of tools, but in retrospect it was pretty horrible. :-)

Well, yeah, I agree. But ... my point was elsewhere. I did *not* change 
string comparison to be case-insensitive; if you look at the code you 
will see that the request is to be case-sensensitive, and if that's the 
case I think we better honor it!

My point (to repeat it, hopefully making it clearer now) is that for a 
case-*sensitive* comparison I used the so-called CaseSensitiveOrder, 
assuming that this would basically be equivalent to plain AsciiOrder. 
But it isn't, and the comparison provided by Case*Sensitive*Order can 
hardly be called case-*sensitive*. My question is: Who defined 
CaseSensitiveOrder that way, and is there anyone who relies on that 
particular CaseSensitiveOrder. If not, I'd rather get rid of it.

We might still decide to have the default be case-insensitive comparison 
though (but again, this is unrelated to the above and could be achieved 
easily by other means).

Cheers,
   - Andreas