This is the mail archive of the
mailing list for the GCC project.
Re: Rename C files to .c in GCC source
- From: David Malcolm <dmalcolm at redhat dot com>
- To: "Kevin Ingwersen (Ingwie Phoenix)" <ingwie2000 at googlemail dot com>
- Cc: DJ Delorie <dj at redhat dot com>, pinskia at gmail dot com, gcc at gcc dot gnu dot org, Jonny Grant <jg at jguk dot org>
- Date: Mon, 02 Feb 2015 11:17:41 -0500
- Subject: Re: Rename C files to .c in GCC source
- Authentication-results: sourceware.org; auth=none
- References: <CAGc9EveH8c7WfQPmDEjrCpSOmxabAECGRBC8T8NUiHbSz2QNmw at mail dot gmail dot com> <EE340ECC-F8A5-49B5-9C83-CD616BC1DDAF at gmail dot com> <xnlhkkx80o dot fsf at greed dot delorie dot com> <C5FA6467-A929-40A0-9DB0-E6A4F20E631B at googlemail dot com>
On Fri, 2015-01-30 at 23:24 +0100, Kevin Ingwersen (Ingwie Phoenix)
> > Am 30.01.2015 um 22:39 schrieb DJ Delorie <firstname.lastname@example.org>:
> > email@example.com writes:
> >> No because they are c++ code so capital C is correct.
> > However, we should avoid relying on case-sensitive file systems
> > (Windows) and use .cc or .cxx for C++ files ("+" is not a valid file
> > name character on Windows, so we can't use .c++).
> Appleâs HFS is, on a default OS X install, case insensitive. But .c++
> is valid. .cxx sounds pretty straight forward to me, since people also
> use the $CXX variable.
FWIW this bit the gcc-python-plugin when someone tried to build it on OS
X: I had a "foo.c" and a "foo.C" in the same directory, with different
content (can't remember the actual names, I think they were one of my
IIRC this confused *git* on OS X no end (only one file could exist in
the working copy at once), until I fixed it by renaming the .C file
This error (albeit on my part) has rather turned me off ".C" files; I
use ".cc" in my own projects these days, fwiw. I think as a general
rule one should avoid upper case in filename suffixes, for this kind of