This is the mail archive of the
mailing list for the GCC project.
Re: Switching to C++ by default in 4.8
- From: Eric Botcazou <ebotcazou at adacore dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Bernd Schmidt <bernds at codesourcery dot com>, gcc at gcc dot gnu dot org, Miles Bader <miles at gnu dot org>, Torvald Riegel <triegel at redhat dot com>, Xinliang David Li <davidxl at google dot com>, Richard Guenther <richard dot guenther at gmail dot com>, Gabriel Dos Reis <gdr at integrable-solutions dot net>, David Edelsohn <dje dot gcc at gmail dot com>, Diego Novillo <dnovillo at google dot com>
- Date: Wed, 11 Apr 2012 10:06:07 +0200
- Subject: Re: Switching to C++ by default in 4.8
- References: <4F7B356E.email@example.com> <firstname.lastname@example.org> <20120411070150.GM6148@sunsite.ms.mff.cuni.cz>
> But IMHO not sufficient for a switch. The GCC C++ proponents should do
> more on a branch to convince. Yes, the syntactic suger for vec.h isn't
> very nice, but the actual implementation is very clever and heavily tuned
> for GCC's needs; if we convert to C++ just because of vec.[ch], we open
> ourselves to what is being discussed in this thread, people who would like
> to turn GCC codebase into yet another LLVM, which not everybody finds
> actually very readable and maintainable code, would start doing so.
Maybe, but if we don't convert vec.[ch], there is no point in using C++ at all.
We could put in place a strict containment policy: no one is allowed to write
non-C code for modules that haven't been explicitly approved. Conversions on
a module level are done on a branch and merged into mainline as a whole. And
state prominently that there is no long term goal towards a complete rewrite
of the compiler in full-blown C++, so that people don't waste time making big
plans for such a rewrite.