Earnie Boyd wrote:
>There is an compile time filter. I forget the exact name, but
>INSENSITIVE is part of the name.
>NOTE: GCC itself thinks that foo.C is a C++ file and thus should be C++
This is true, but surely, only to the extent that it is dependent on the
case used to type the file.C argument on the GCC command line.
If it were otherwise, GCC could not compile regular .c files on systems
such as OpenVMS, or even MS-DOS, where the file systems are *neither*
case sensitive *nor* case retentive; on these systems all file names
are recorded in their directories, using upper case exclusively, so
FILE.C is, presumably, a regular .c file.
I know GCC has been ported to OpenVMS, and there is the DJGPP port for
MS-DOS. I believe, but am unable to verify, that these *do* handle the
file.c and file.C distinction as above. GNU make is also available for
these systems, and works in an entirely case insensitive manner, WRT
file name matching, on both.
I think, what I am trying to say here is, that, given the default case
insensitive nature of MS-Windows file system, perhaps there is a good
argument in favour of building MSYS make with case insensitive file
name matching as its default behaviour. And, I guess, Earnie is also
saying "if that's the way you want it, then feel free to build it that
way yourself"; perhaps, when I get a bit of spare time, whatever that
is, I will have a go! For now, I think I will stick with the work
around based on the .PRECIOUS trick, that I discovered, and posted,