This is the mail archive of the
mailing list for the GCC project.
Re: Using C++ in GCC is OK
- From: Thomas Neumann <tneumann at users dot sourceforge dot net>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 31 May 2010 22:51:33 +0200
- Subject: Re: Using C++ in GCC is OK
- Connect(): No such file or directory
- Followup-to: gmane.comp.gcc.devel
- References: <4C030228.firstname.lastname@example.org>
> Because C++ is a big language, I think we should try to enumerate what
> is OK, rather than what is not OK.
> Is there anyone who would like to volunteer to develop the C++ coding
I hope you you don't mind my question (as I am currently not an active GCC
developer), but what is the point of this? I understand why you do not want
to have sudden, disruptive changes to a large existing code base, so any
introduction of C++ features should be careful and controlled, but why
artificially eliminate parts of the language?
I personally think the coding standard should be: "All C++ code has to be 1)
easily readable, 2) easily maintainable, and 3) produce efficient machine
code and conserve memory. Apart from that use ISO/IEC 14882-1998".
Now I know that this is totally unrealistic in the context of the GCC
project, and some people here get really nervous about a potential C++
creep, but IMHO artificial limitations on a pure syntax base are not really
meaningful. One should look at the consequences and not at the syntax.