This is the mail archive of the
mailing list for the GCC project.
Re: Rename C files to .c in GCC source
- From: "Kevin Ingwersen (Ingwie Phoenix)" <ingwie2000 at googlemail dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: DJ Delorie <dj at redhat dot com>, Andrew Pinski <pinskia at gmail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Jonny Grant <jg at jguk dot org>
- Date: Sat, 31 Jan 2015 06:30:39 +0100
- 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> <CAH6eHdRxDNVgguGia9uckGGc913Hj1pOAFfmMuQR2Pc1gEyLEQ at mail dot gmail dot com>
> Am 31.01.2015 um 02:57 schrieb Jonathan Wakely <firstname.lastname@example.org>:
> On 30 January 2015 at 22:24, Kevin Ingwersen (Ingwie Phoenix) wrote:
>> Appleâs HFS is, on a default OS X install, case insensitive.
> Which doesn't matter, see my previous reply.
That is true; though its good to keep an eye out for it.
>> But .c++ is valid. .cxx sounds pretty straight forward to me, since people also use the $CXX variable.
> We already use .C and .cc in GCC sources, so even if we needed to
> change it, it would probably be better to use .cc for consistency
> rather than add a third extension.
Oh, I did not know this detail since I havenât peered into the GCC source in a felt forever. Would make sense to use .cc then if it has already been used elsewhere in the source.