Hi,
On Tue, Jul 30, 2013 at 07:13:22AM -0400, Diego Novillo wrote:
> On Tue, Jul 30, 2013 at 5:04 AM, Marek Polacek <pola...@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... That might be pain for people who are used to do
> > 'grep foo gcc/*.c' and suchlike.
>
> Any issues with doing a mass rename then?
>
Well, IIRC mostly worries about history. SVN claims to be able to
track history of renamed files but I use the git mirror now and I
wonder what the history would show there. I would consider it very
unfortunate if 'git blame' did not show the .c era history of the
renamed files. But maybe it would just work.
I think that proponents of this idea should make some experiments
along these lines to estimate the cost. OTOH, I think the time can be
spent better (and that is also the reason why I will not fight about
this beyond writing this message).
As far as newbies are concerned, I think that grasping that .c files
are C++ files is one of the easy things to learn about GCC compared to
other necessary knowledge (which is something we should work on).
If the problem is that your emacs opens gcc files in C mode instead of
C++, add this to your .emacs file:
(add-to-list 'auto-mode-alist '("gcc/.+\\.[ch]\\'" . c++-mode))
Even after a rename you would have to do something like that for the
.h files anyway.
Thanks,
Martin
