On Fri, 23 Apr 2010 12:33:10 +1200 Greg Ewing <greg.ewing@canterbury.ac.nz> wrote:
Mike Meyer wrote:
If the user typed the filename "foo.c" and I am trying to decide if it has the ".C" extension. If "foo.C" exists on the disk and the user knows that "foo.c" and "foo.C" are the same file, it's reasonable for the user to expect the application to figure out that this file has the ".C" extension, even though they typed ".c". But you don't know whether the user is expecting this. If he knows that gcc distinguishes between .c and .C, it may be that he is expecting foo to be compiled as a C file rather than C++, and he made a mistake when he named the file foo.C.
Given that the argument for making the test case-insensitive to start with was that the user expects .JPG and .jpg to be the same, I think you just shot down the case for making the test case-insensitive as well. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org