Re: Do we need parsers?

Stefan Monnier <monnier+/news/comp/compilers@tequila.cs.yale.edu>
17 May 1997 00:07:51 -0400

          From comp.compilers

Related articles
Do we need parsers? john@dwaf-hri.pwv.gov.za (John Carter) (1997-05-13)
Re: Do we need parsers? thetick@scruz.net (Scott Stanchfield) (1997-05-15)
Re: Do we need parsers? dgay@barnowl.CS.Berkeley.EDU (1997-05-16)
Re: Do we need parsers? monnier+/news/comp/compilers@tequila.cs.yale.edu (Stefan Monnier) (1997-05-17)
Re: Do we need parsers? monnier+/news/comp/compilers@tequila.cs.yale.edu (Stefan Monnier) (1997-05-17)
Re: Do we need parsers? thetick@scruz.net (Scott Stanchfield) (1997-05-19)
Re: Do we need parsers? David.Monniaux@ens-lyon.fr (1997-05-22)
Re: Do we need parsers? john@dwaf-hri.pwv.gov.za (John Carter) (1997-05-22)
Re: Do we need parsers? nkramer@jprc.com (Nick Kramer) (1997-05-30)
Re: Do we need parsers? dgay@barnowl.CS.Berkeley.EDU (1997-06-04)
| List of all articles for this month |

From: Stefan Monnier <monnier+/news/comp/compilers@tequila.cs.yale.edu>
Newsgroups: comp.compilers
Date: 17 May 1997 00:07:51 -0400
Organization: Compilers Central
References: 97-05-158 97-05-189
Keywords: parse, tools

Scott Stanchfield <thetick@scruz.net> writes:
> above. "Watches what was typed." Sounds like a scanner to me, but it
> scans the typed keys instead of a file. "Grouping nodes into subtrees"
> sounds like parsing to me. But instead of traditional "tokens" we pass


But it might look pretty different from lex/yacc technology. For
instance "if" could be a mere sequential combination of keys calling a
function ( la "local-set-key") that inserts an "if" statements
(with the user's favorite syntax): the syntax is not input but output
(which among other things implies that it could totally be ambiguous
with the only inconvenient being that the user wouldn't be able to
tell the exact meaning without looking more closely (switching syntax,
for instance)).


                Stefan
--


Post a followup to this message

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