Re: Case insensitivity ad nauseum

[Kevin Layer]

Jim.Hyslop <Jim.Hyslop@Leitch.com> wrote:

>> ...
>> is it generally considered
>> bad practise to have two files with the same name, that differ only by case,
>> in the same directory? 

Yes.

>> My understanding is that the common practise on Unix
>> is to use all lower-case names, to avoid potential confusion. 

I've been using UNIX since the BSD 4.x days ('82).  I've never heard
this before.

>> Sounds to me
>> like this is a manually-operated (and therefore error-prone) convention
>> imposed in order to have, effectively, a case-insensitive, case-preserving
>> file naming system ;-)

Bad conclusion.

>> Let's build software that works the way people expect. On a
>> case-insensitive, case-preserving file system such as Windows or (I believe)
>> Mac OS, 

But not Mac OS X.

>> that means making the program smart enough to realize that "cvs rlog
>> myproject" also means "cvs rlog MyProject". If you put it in, you
>> unfortunately won't get a lot of Windows users saying "thank you for making
>> it match the case", but if you leave it out you might get a lot of Windows
>> users saying "WTF? Why am I getting an error with 'cvs rlog myproject'?
>> Whaddya mean it's case-sensitive?!? What a stupid program!!"

If Windows is case preserving and people use dual case in names, why
allow them to be sloppy and specify the single case name?  The only
thing you are doing is supporting fuzzing thinking, IMO.

Kevin