This is the mail archive of the gcc@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: Putting C++ code into gcc front end

From: Neil Booth <neil at daikokuya dot co dot uk>
To: Pop S?bastian <pop at gauvain dot u-strasbg dot fr>
Cc: Per Bothner <per at bothner dot com>, tromey at redhat dot com,GCC Hackers <gcc at gcc dot gnu dot org>
Date: Fri, 7 Mar 2003 20:23:16 +0000
Subject: Re: Putting C++ code into gcc front end
References: <Pine.LNX.4.33.0303041555460.5124-100000@wotan.suse.de> <3E64C09A.9070500@comsys.se> <87isuzjb71.fsf@fleche.redhat.com> <3E67FBA6.1000907@bothner.com> <20030307125056.GA23848@gauvain.u-strasbg.fr>

Pop S?bastian wrote:-

> On Thu, Mar 06, 2003 at 05:53:42PM -0800, Per Bothner wrote:
> > Personally, I'd love to re-write all of Gcc in C++,
> > starting with using inheritance for tree nodes, so
> > we can actually get some static type-checking.

Really, why does everything have to be shoehorned into being a tree?
Decls, expressions, scopes / symbol tables, statements etc should
all be their own data type.  We can get perfectly good type checking
in C if we don't insist the universe is made up of trees.

cpplib hasn't made everything a tree.  There's no reason for everything
to be a tree in the front ends either.

Neil.

Follow-Ups:
- Re: Putting C++ code into gcc front end
  - From: Per Bothner
- Re: Putting C++ code into gcc front end
  - From: Geoff Keating

References:
- Re: Putting C++ code into gcc front end
  - From: Michael Matz
- Re: Putting C++ code into gcc front end
  - From: Lars Segerlund
- Re: Putting C++ code into gcc front end
  - From: Tom Tromey
- Re: Putting C++ code into gcc front end
  - From: Per Bothner
- Re: Putting C++ code into gcc front end
  - From: Pop Sébastian

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