Linked by Thom Holwerda on Tue 1st Jun 2010 15:12 UTC
General Development "I am pleased to report that the GCC Steering Committee and the FSF have approved the use of C++ in GCC itself. Of course, there's no reason for us to use C++ features just because we can. The goal is a better compiler for users, not a C++ code base for its own sake. Before we start to actually use C++, we need to determine a set of coding standards that will apply to use of C++ within GCC."
Thread beginning with comment 427720
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Benefits
by lemur2 on Wed 2nd Jun 2010 11:57 UTC in reply to "Benefits"
Member since:

Wondering on what benefits for the users of libraries and end users of applications would be?

Let's say I'm using GCC for compiling a program, I've been coding & compiling for years now. Any changes to me or my users?

Maybe introducing new concepts to GCC would take less time? hmm, what do you think?

I think it is all about adding new languages to the collection. "gcc" is, after all, the GNU Compiler Collection.

One such new language is Google Go.
Paradigm: compiled, concurrent, imperative, structured

Go claims for itself to have the following desirable characteristics: simple, fast, safe, concurrent, fun and open source. Go is type safe and memory safe ... say good-bye to stack overflows. Go has fast builds, clean syntax, garbage collection, methods for any type, and run-time reflection. Apparently, Go is gaining some level of popularity:
Go entered the TIOBE Programming Community Index at fifteenth place in its first year, surpassing established languages like Pascal.

So how is all this in any way relevant to the topic, you may well ask?

gccgo, which is the gcc frontend program (i.e. compiler) for Go, is itself written in C++.

Hence the need to allow gcc to use C++.

Edited 2010-06-02 12:09 UTC

Reply Parent Score: 2