From: "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT n-o-s-p-a-m DOT ru>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GCC bugs
Date: 20 Jan 2000 20:17:59 GMT
Organization: MTU-Intel ISP
Lines: 38
Message-ID: <01bf6382$c33cc020$LocalHost@alex>
References: <01bf611a$9c6e9500$LocalHost AT alex> <3883BCC2 DOT 2CC1DCD9 AT a DOT crl DOT com> <01bf61c3$70f0a7c0$LocalHost AT alex> <Pine DOT SUN DOT 3 DOT 91 DOT 1000119113628 DOT 9609M-100000 AT is> <01bf627f$0b8075c0$LocalHost AT alex> <20ya9li3gm DOT fsf AT Sky DOT inp DOT nsk DOT su> <01bf6359$2df17020$LocalHost AT alex> <867ctv$i7q$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
NNTP-Posting-Host: dial52183.mtu-net.ru
X-Trace: gavrilo.mtu.ru 948399479 27830 195.34.52.183 (20 Jan 2000 20:17:59 GMT)
X-Complaints-To: usenet-abuse AT mtu DOT ru
NNTP-Posting-Date: 20 Jan 2000 20:17:59 GMT
X-Newsreader: Microsoft Internet News 4.70.1155
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Thanks. But that's too confusing for a man who has always been working in
MS-DOS and MS-Windows. Why DJ implemented this stuff? He has known that
there is no difference between upper and lower case in DOS/Windows? So I
repeat the question: Why? Just for fun? I don't think that such a stuff may
be explained as a compatibility with Unix/Linux/Xenix/whatever... There is
no any compatibility since OS is too different to all these Unixes.

Anyway, thanks once more.

Alexei A. Frounze
-- 
P.S. In order to reply via e-mail, remove the "n-o-s-p-a-m." substring out
of the e-mail address.

Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de> записано в
статью <867ctv$i7q$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>...
> Alexei A. Frounze <alex DOT fru AT mtu-net DOT n-o-s-p-a-m DOT ru> wrote:
> [*.c vs. *.C file]
> 
> Phew, such a long discussion, which could easily have been avoided, if
> you had done as the FAQs suggest: add '-v' to the gcc command line(s)
> and look at the output, or post it here. The difference would have
> been really easy to spot (cc1 vs. cc1plus usage).
> 
> Lesson to take home: don't use *.c or similar wildcards when calling
> gcc directly from command.com or a batch file. They'll turn into *.C,
> automatically.
> 
> > But why output is casesensitive to input file extension???
> 
> Because gcc comes from the world of Unix, where you can have two files
> 'foo.c' and 'foo.C', in the same directory, and they really are
> separate files, not just two way to reach the same file, as in DOS.
> 
> In Unix, '.C' is a filename extensions used for C++ files, and
> different from '.c', which is for C files. This is also clearly
> documented in the gcc docs (node 'Overall Options'):