Re: Case insensitivity ad nauseum

[Paul Sander]

>--- Forwarded mail from jim@fortunet.com

>Jim.Hyslop <Jim.Hyslop@Leitch.com>
>WeLl mAdE ArguMent...

>>No, not at all. For example, of the 111 items in my home directory
>>right now, 17 of them use upper-case letters in a meaningful
>>way. Common practice is to name some things on Unix in a mixture of
>>cases, e.g. Makefile, Imakefile, ChangeLog.

>That's not really the point... how many times do you maintain ChangeLog,
>CHangeLog, changeLog, changelog in the same directory?  or Makefile and
>makefile?  or .BASHrc, .bashRC, .BashRc, .bashrc ?  Is there even one
>example of where it's logical to have the same name with a different case in
>a directory?

I have worked in a shop where most directories contained a "makefile" and a
"Makefile", and relied on the search order of the tools to choose the right
one.  The reason was because the product was a third-party source with its
own makefiles, and we used the second makefile to interface our build
system with theirs.  It was a gunky arrangement, but it saved us from
having to merge local changes into their makefiles after every code drop,
and any changes we made to their makefiles were generic in nature and could
be fed back to them.

>--- End of forwarded message from jim@fortunet.com