This is the mail archive of the
mailing list for the GCC project.
Re: Rename C files to .c in GCC source
- From: Jonny Grant <jg at jguk dot org>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: "Kevin Ingwersen (Ingwie Phoenix)" <ingwie2000 at googlemail dot com>, Eli Zaretskii <eliz at gnu dot org>, Jonathan Wakely <jwakely dot gcc at gmail dot com>, DJ Delorie <dj at redhat dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Tue, 03 Feb 2015 22:55:31 +0000
- 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> <CAH6eHdTkWCa4vK=HVVaJaa1dihs4gdjX+u87Q_GO358752Tjkw at mail dot gmail dot com> <83bnldipfo dot fsf at gnu dot org> <2566D022-F1C4-48CE-BA29-92F120D1F758 at googlemail dot com> <54CFE7FC dot 5070102 at jguk dot org> <CA+=Sn1mNVvyacB0ZnHw7HJ9W-ntMARzSxS8QAik=R=K_79-vzA at mail dot gmail dot com>
On 02/02/15 21:18, Andrew Pinski wrote:
On Mon, Feb 2, 2015 at 1:11 PM, Jonny Grant <firstname.lastname@example.org> wrote:
On 01/02/15 16:34, Kevin Ingwersen (Ingwie Phoenix) wrote:
Am 01.02.2015 um 17:09 schrieb Eli Zaretskii <email@example.com>:
Date: Sat, 31 Jan 2015 01:55:29 +0000
From: Jonathan Wakely <firstname.lastname@example.org>
Cc: Andrew Pinski <email@example.com>, "firstname.lastname@example.org"
<email@example.com>, Jonny Grant <firstname.lastname@example.org>
These files are only compiled by GCC's own build system, with GCC's
own makefiles, so we know we invoke the C++ compiler and so the
language isn't inferred from the file extension, and so we aren't
relying on case-sensitive file systems.
That is true for building GCC. But what about editors and other
development tools? They _will_ be affected.
Indeed. Atom keeps thinking .C is an actual âANSI Câ thing. If I were to
make a suggestion to the GCC devâs, then I probably could also swiftly word
$ find gcc-src -name "*.Câ | while read f; do mv $f $(echo $f | sed
In other words; .cxx, .cpp or .cc seems like a solution that works across
platforms. Since .cc is already used at some places, I would recommend that
this is to be the extension to choose.
One does not neccessarily need to make a dev apply hacks all over just to
Is this a consensus agreement to rename those .C -> .cc ?
There are around 11k files that have the .C ending to them; all in the
testsuite. I don't think it make sense to move them.
How many minutes labor is this task?