Re: Why separate Lexical & Parser Generators

pardo@cs.washington.edu (David Keppel)
Tue, 11 Oct 1994 18:27:51 GMT

          From comp.compilers
Related articles
[2 earlier articles]
Re: Why separate Lexical & Parser Generators leichter@zodiac.rutgers.edu (1994-10-06)
Re: Why separate Lexical & Parser Generators morrison@hal.cs.uiuc.edu (1994-10-07)
Re: Why separate Lexical & Parser Generators johnl@cs.indiana.edu (John Lacey) (1994-10-10)
Re: Why separate Lexical & Parser Generators hagerman@ece.cmu.edu (1994-10-10)
Re: Why separate Lexical & Parser Generators wrs@apple.com (Walter Smith) (1994-10-10)
Re: Why separate Lexical & Parser Generators cef@geodesic.com (Charles Fiterman) (1994-10-11)
Re: Why separate Lexical & Parser Generators pardo@cs.washington.edu (1994-10-11)
Re: Why separate Lexical & Parser Generators johnl@cs.indiana.edu (John Lacey) (1994-10-12)
Re: Why separate Lexical & Parser Generators hagerman@ece.cmu.edu (1994-10-14)
Re: Why separate Lexical & Parser Generators adrian@platon.cs.rhbnc.ac.uk (1994-10-21)
Re: Why separate Lexical & Parser Generators hbaker@netcom.com (1994-10-22)
| List of all articles for this month |
Newsgroups: comp.compilers
From: pardo@cs.washington.edu (David Keppel)
Keywords: parse, design
Organization: Computer Science & Engineering, U. of Washington, Seattle
References: 94-10-028 94-10-079
Date: Tue, 11 Oct 1994 18:27:51 GMT

>>[Why separate lexer and parser generators?]
>[Error messages can appear anywhere.]


Perhaps I'm missing something, but the problem of ``errors can appear
anywhere'' sounds like an argument for separate _lexers and parsers_,
but no requirement that the lexers and parsers need to be built using
distinct tools. For example, you could build a lexer using `yacc' and
then build a parser, also using `yacc', that calls the lexer to get
input tokens.


;-D on ( Bisonity-Bison, Don't Talk Tyson ) Pardo
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.