Related articles |
---|
Why separate Lexical & Parser Generators heronj@smtplink.NGC.COM (John Heron) (1994-10-05) |
Re: Why separate Lexical & Parser Generators andand@csd.uu.se (Anders Andersson) (1994-10-06) |
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) |
[2 later articles] |
Newsgroups: | comp.compilers |
From: | "John Lacey" <johnl@cs.indiana.edu> |
Keywords: | parse, history, algol60 |
Organization: | Computer Science, Indiana University |
References: | 94-10-028 94-10-058 |
Date: | Mon, 10 Oct 1994 03:33:18 GMT |
morrison@hal.cs.uiuc.edu (Vance Morrison) writes:
>Another problem is dealing with comments because they can occur ANYWHERE.
>This can be solved by simply restricting where comments can go (which may
>not be a bad idea in any case).
For a historical note, the Algol 60 report has this problem. The
grammar given is complete, with only characters as terminals. They
not only restrict comments, which may occur only after a semi-colon,
begin, or end, but in addition elide comments from the grammar, and
describe them separately. They are described not in BNF, but as a set
of transformations on sequences of tokens.
John L
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.