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

From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
To: Neil Booth <neil at daikokuya dot co dot uk>
Cc: Zack Weinberg <zack at codesourcery dot com>, Nathanael Nerode <neroden at twcny dot rr dot com>, gcc-patches at gcc dot gnu dot org
Date: 10 Jan 2003 13:28:21 +0100
Subject: Re: ANSIfy cp/parser.c
Organization: Integrable Solutions
References: <20030109030342.GA20609@doctormoo><87bs2r0wpv.fsf@egil.codesourcery.com><20030109065216.GA26264@daikokuya.co.uk><20030109213019.GA735@daikokuya.co.uk>

Neil Booth <neil@daikokuya.co.uk> writes:

[ ... many things I generally agree with...]

| o Create a re-entrant recursive descent parser that looks somewhat
|   like cp/parser.c, in gcc/parser.c.

Please, if you're going to "lift" the C front-end, please, first do
move the C front-end bits in a separate directory; just like
other front-ends.  That would improve a bit the organization of the
files iin gcc/.

| o Have it generate a simple, high-level C IR (with real types, not the
|   "everything is a tree" paradigm)

Yeah, the topic of going away from the "everything is a tree" paradigm
has been sporadically mentioned, but there seems to be no much thought
on it...

-- Gaby

Follow-Ups:
- Re: ANSIfy cp/parser.c
  - From: Neil Booth

References:
- ANSIfy cp/parser.c
  - From: Nathanael Nerode
- Re: ANSIfy cp/parser.c
  - From: Zack Weinberg
- Re: ANSIfy cp/parser.c
  - From: Neil Booth
- Re: ANSIfy cp/parser.c
  - From: Neil Booth

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