This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New file extension
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Marek Polacek <polacek at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 30 Jul 2013 11:03:08 -0500
- Subject: Re: New file extension
- References: <CAAiZkiBbBe1YwUS+NP8hP-yCAZhEa-6VGXkhKLkRF3QrgWy_wA at mail dot gmail dot com> <20130729200826 dot GA31944 at virgil dot suse> <20130730090434 dot GF17022 at redhat dot com>
On Tue, Jul 30, 2013 at 4:04 AM, Marek Polacek <polacek@redhat.com> wrote:
> On Mon, Jul 29, 2013 at 10:08:26PM +0200, Martin Jambor wrote:
>> I do not care very much but I disagree. Having some files with .c
>> suffix and some with .cc suffix would imply some sort of difference
>> where there is going to be none.
>
> Yeah -- this sort of discrepancy I don't like either. In gcc/, we
> have 362 .c files and 0 .cc files, so every new .cc file will step out
> of line...
Any thing *new* steps out of line for someone.
Putting C++ programs in .c file is out of line for most people,
including the newcomers that people worry about.
For many tools, including editors, .c is a C file, not a C++ file,
so you don't get the benefit of working with a C++ program.
> That might be pain for people who are used to do
> 'grep foo gcc/*.c' and suchlike.
>
> Marek