Re: Putting C++ code into gcc front end

[Zack Weinberg <zack at codesourcery dot com>]

Benjamin Kosnik <bkoz at redhat dot com> writes:

>> I think the only really controversial question would be whether to allow
>> partial specialization of templates. Everything else is a clear yes or a
>> clear no.
>
> Please, let's stay on topic. Tom has requested, and has a valid need for:
>
> 1) full C++ class semantics, including construction/destruction
> 2) exception handling
>
> I don't think it's necessary to debate that these requests are
> reasonable, nor do I think it is necessary to define at this moment what
> is acceptable use, now or in the future: that's for maintainers in the
> future to deal with. These kind of limitations are precisely what has
> put this whole question on the table.

Everyone in this discussion is talking about *which* C++ features
should be allowed, which is orthogonal to my original concern on this
score.  My concern is entirely about *where* C++ can safely be used,
and my opinion at the present time is "only in front ends other than
C/C++/Ada."  We can easily arrange to have a fully functional g++ and
libstdc++ available when those front ends are built, starting with
only a C compiler.  We can *not* easily ask everyone who currently
builds GCC to install a C++ compiler for bootstrap purposes.  I am
personally familiar with an organization that still uses gcc 2.7.2 as
a starting point for GCC builds.  That's a bit extreme, but still.

zw