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: EOF character in parser

From: neil at daikokuya dot co dot uk
To: Geert Bosch <bosch at gnat dot com>
Cc: gagneet at acmet dot com, DJ Delorie <dj at redhat dot com>, gcc at gcc dot gnu dot org,Zack Weinberg <zack at codesourcery dot com>, wilson at specifixinc dot com
Date: Wed, 7 Jan 2004 06:48:45 +0000
Subject: Re: EOF character in parser
References: <1072501124.14935.ezmlm@gcc.gnu.org> <006a01c3cd48$55e00530$9900a8c0@GAGNEET> <3FFA0A09.8000104@specifixinc.com> <200401060115.i061FSfr025053@greed.delorie.com> <87llol2675.fsf@egil.codesourcery.com> <1F666FE0-3FF5-11D8-A9E6-000A959A128E@gnat.com> <20040106221613.GA7753@daikokuya.co.uk> <493ABB2D-40B8-11D8-AA4F-000A959A128E@gnat.com>

Geert Bosch wrote:-

> On Jan 6, 2004, at 17:16, neil@daikokuya.co.uk wrote:
> >There is no EOF character in cpplib; all bytes are "OK", so this
> >doesn't work.
> 
> You can still take advantage of knowing there's an EOF at the
> end of the file. Most tokens cannot contain the EOF symbol and
> you can optimize scanning of those tokens. Or more general, you
> could scan as if EOF's are not allowed in the source. Then you
> fix up when you actually find an EOF.

Yeah, I'd misread your mail.  That is in fact what cpplib does
(with \n as sentinel).

Neil.

References:
- Re: EOF character in parser
  - From: Jim Wilson
- Re: EOF character in parser
  - From: DJ Delorie
- Re: EOF character in parser
  - From: Zack Weinberg
- Re: EOF character in parser
  - From: Geert Bosch
- Re: EOF character in parser
  - From: neil
- Re: EOF character in parser
  - From: Geert Bosch

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