This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Putting C++ code into gcc front end
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Olivier Galibert <galibert at pobox dot com>
- Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, Richard dot Earnshaw at arm dot com, Rupert Wood <me at rupey dot net>, gcc at gcc dot gnu dot org
- Date: Tue, 04 Mar 2003 14:19:51 +0000
- Subject: Re: Putting C++ code into gcc front end
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> On Tue, Mar 04, 2003 at 01:13:39PM +0100, Gabriel Dos Reis wrote:
> > I have no idea of how many GNU extensions there are. Your question is
> > probably one of the most important ones to answer.
>
> Or, the other way around, what about requiring a system C++ compiler
> and start using C++[1] in all the front and back ends where useful ?
>
> OG.
>
> [1] Maybe not all of C++ immediatly, of course.
Fixing the current c++ compiler so that it can be compiled with any ISO C
compiler is a completely different level of change from permitting C++
everywhere. Just at this point it isn't reasonable to assume that there
are conforming (even sufficiently conforming) C++ compilers widely
available on the wide range of hosts that GCC currently supports.
Anyway defining a suitable subset of C++ that we could expect is
1) hard -- we don't know enough about all the c++ compilers out there.
2) impossible to enforce rigorously without modifying the compiler to
allow us to detect extensions from the subset.