This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Rename C files to .c in GCC source
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: dj at redhat dot com, pinskia at gmail dot com, gcc at gcc dot gnu dot org, jg at jguk dot org
- Date: Sun, 01 Feb 2015 18:09:31 +0200
- 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>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 31 Jan 2015 01:55:29 +0000
> From: Jonathan Wakely <jwakely.gcc@gmail.com>
> Cc: Andrew Pinski <pinskia@gmail.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, Jonny Grant <jg@jguk.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.