Re: Why are LR parsers faster than using if conditions

Tomasz Zielonka <t.zielonka@zodiac.mimuw.edu.pl>
25 Jun 2004 01:52:19 -0400

          From comp.compilers
Related articles
Why are LR parsers faster than using if conditions shripal.meghani@philips.com (2004-06-06)
Re: Why are LR parsers faster than using if conditions torbenm@diku.dk (2004-06-09)
Re: Why are LR parsers faster than using if conditions alexc@std.com (Alex Colvin) (2004-06-11)
Re: Why are LR parsers faster than using if conditions cdc@maxnet.co.nz (Carl Cerecke) (2004-06-15)
Re: Why are LR parsers faster than using if conditions cdc@maxnet.co.nz (Carl Cerecke) (2004-06-21)
Re: Why are LR parsers faster than using if conditions t.zielonka@zodiac.mimuw.edu.pl (Tomasz Zielonka) (2004-06-25)
Re: Why are LR parsers faster than using if conditions haberg@matematik.su.se (Hans Aberg) (2004-06-26)
Re: Why are LR parsers faster than using if conditions haberg@matematik.su.se (Hans Aberg) (2004-06-28)
Re: Why are LR parsers faster than using if conditions clint@0lsen.net (Clint Olsen) (2004-06-28)
Re: Why are LR parsers faster than using if conditions tmoog@panix.com (2004-06-30)
Re: Why are LR parsers faster than using if conditions haberg@matematik.su.se (Hans Aberg) (2004-06-30)
Re: Why are LR parsers faster than using if conditions christian.bau@cbau.freeserve.co.uk (Christian Bau) (2004-07-11)
[2 later articles]
| List of all articles for this month |
From: Tomasz Zielonka <t.zielonka@zodiac.mimuw.edu.pl>
Newsgroups: comp.compilers
Date: 25 Jun 2004 01:52:19 -0400
Organization: MIMUW
References: 04-06-012 04-06-034 04-06-072
Keywords: parse, optimize
Posted-Date: 25 Jun 2004 01:52:19 EDT

Carl Cerecke wrote:
> Basically, "hard-coded" means that the LR state machine is expanded out
> into code, and shifts are coded as gotos between the code chunks. This
> works well for C, but not so good for Java or python, which don't have
> gotos (See! There *is* a reason for having gotos in a language!).


(or tail-call elimination)


Best regards,
Tom


--
.signature: Too many levels of symbolic links

Post a followup to this message

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