This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Push GENERIC farther into C/C++ front ends.


Tom Tromey wrote:

"Jason" == Jason Merrill <jason@redhat.com> writes:


Jason> IIRC Gaby sent a patch to avoid using C++ keywords, which I
Jason> supported and Mark didn't.  I don't think it was ever checked
Jason> in.

I could understand not wanting to support compiling the whole front
end with a C++ compiler -- after all, the source language is C.  But
what about making the headers C++-safe, so that a front end could be
written in C++ if one so desired?

I've been experimenting with this lately.  Right now the block is that
struct real_value has a field named `class'.  That's easily fixed, but
given the above I'm wondering whether it will be acceptable...?

If I recall correctly, my concern was that it might be hard to maintain the invariant that the code compile as C++. Therefore, I think that what I'd want is to make it a goal that stuff compile as C++, but not try to make people check that when making changes.


--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]