This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: File extensions for C++ source?
On Sat, Nov 29, 2003 at 11:58:54AM -0500, Daniel Jacobowitz wrote:
>On Sat, Nov 29, 2003 at 05:52:02PM +0100, Gabriel Dos Reis wrote:
>> kaih@khms.westfalen.de (Kai Henningsen) writes:
>>
>> | gdr@integrable-solutions.net (Gabriel Dos Reis) wrote on 29.11.03 in <m3ptfb7b9u.fsf@uniton.integrable-solutions.net>:
>> |
>> | > even Windows nowadays recognizes much more
>> | > elaborated filenames than we do on Unixes.
>> |
>> | This is utter nonsense.
>>
>> As usual, I would not have expected something different in a
>> followup from you.
>>
>> | And unless a program uses unusual methods, Windows *still* has case
>> | insensitive filenames.
>>
>> I can access Windows partition (from Linux) on my machine and I can
>> telle you what the filenames I create look like. At the very least,
>> they are case-sensitive. And I'm not using an unusual method.
>
>I don't know the state of the art on NTFS, which Linux does not support
>well, but FAT32 only _appears_ to be case sensitive: it records the
>case of the filename, but any other case will refer to the same file.
NTFS is similar. So, if you create "foo.c", you can refer to it as
"foo.C" on FAT32 or NTFS filesystems. The first time you create a file
you'll the filename will have case you used but you cAn REfEr tO IT
usinG AnY cAsE. There are ways to create true case sensitive file names
on NTFS partitions but support for this is limited.
And, as has been (somewhat rudely) pointed out above, Windows *is* more
limited in what characters can be used in its filenames than UNIX/linux.
FWIW, Cygwin now has a "managed mode" which allows true case sensitivity
but it does that by munging filenames behind the scenes so it is
obviously not something you can rely or insist on.
cgf