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: ANSIfy cp/parser.c


Neil Booth wrote:
Per Bothner wrote:-
In fact, there may be maintainance advantages to having a *single*
executable thta handles C, C++, ObjC and ObjC++.

If you really mean executable,
I do.  I'm not sure it would be the Right Thing, but I believe
there are existing compiler that use the same executable for C
and C++.  It makes sense if you subscribe to the belief that
C is "mostly a superset of C", in which case you might as well
use the C++ compiler to compile C, just turn off C++-isms.
Rather like using the same executable to process both pre-processed
and non-preprocessed code.

But sharing source code of course the much more important goal.

there's nothing stopping us having
2 different parsers in a single executable.
True, but that would reduce the point of using a single executable.
--
	--Per Bothner
per@bothner.com   http://www.bothner.com/per/


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