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: Neil Booth <neil at daikokuya dot co dot uk>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Per Bothner <per at bothner dot com>, gcc-patches at gcc dot gnu dot org
Date: Fri, 10 Jan 2003 06:47:23 +0000
Subject: Re: ANSIfy cp/parser.c
References: <20030109030342.GA20609@doctormoo> <87bs2r0wpv.fsf@egil.codesourcery.com> <20030109065216.GA26264@daikokuya.co.uk> <20030109213019.GA735@daikokuya.co.uk> <3E1DF443.1000604@bothner.com> <20030109222016.GB1951@daikokuya.co.uk> <3E1E28BC.60500@bothner.com> <87k7hdg2rm.fsf@egil.codesourcery.com>

Zack Weinberg wrote:-

> > It would also be nice if the parser(s) were re-entrant, like cpplib.
> 
> Yes, except that there has never been a user of cpplib's notional
> reentrancy and therefore we don't know if it actually works.  I'm
> inclined to call YAGNI.

YAGNI?  Yet another good? ...?

I'm writing mine like Mark did his; it will be re-entrant.  Unlike
cpplib parsers are recursive, so it is more obviously useful in this
case.

Neil.

Follow-Ups:
- Re: ANSIfy cp/parser.c
  - From: Zack Weinberg

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
- Re: ANSIfy cp/parser.c
  - From: Per Bothner
- Re: ANSIfy cp/parser.c
  - From: Neil Booth
- Re: ANSIfy cp/parser.c
  - From: Per Bothner
- Re: ANSIfy cp/parser.c
  - From: Zack Weinberg

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