Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| precedences vs. hierarchy bassobajo@gmail.com (Andreas Schramm) (2016-06-06) |
| Re: precedences vs. hierarchy mailbox@dmitry-kazakov.de (Dmitry A. Kazakov) (2016-06-06) |
| Re: precedences vs. hierarchy gneuner2@comcast.net (George Neuner) (2016-06-06) |
| Re: precedences vs. hierarchy federation2005@netzero.com (2016-06-06) |
| precedences vs. hierarchy slkpg4@gmail.com (SLK Mail) (2016-06-07) |
| Re: precedences vs. hierarchy 545-066-4921@kylheku.com (Kaz Kylheku) (2016-06-07) |
| Re: precedences vs. hierarchy mailbox@dmitry-kazakov.de (Dmitry A. Kazakov) (2016-06-07) |
| Re: precedences vs. hierarchy anton@mips.complang.tuwien.ac.at (2016-06-08) |
| From: | "SLK Mail" <slkpg4@gmail.com> |
| Newsgroups: | comp.compilers |
| Date: | Tue, 07 Jun 2016 08:53:41 -0800 |
| Organization: | SLK Systems |
| Injection-Info: | miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="24426"; mail-complaints-to="abuse@iecc.com" |
| Keywords: | parse |
| Posted-Date: | 07 Jun 2016 10:55:13 EDT |
Using precedence parsing keeps the grammar, and so the parser smaller and
also easier to read. The size was much more important when memory was
measured in kilobytes, not in gigabytes. It also eliminates the empty
precedence transitions at runtime, though this is easy to do by reducing
the parse tree before creating the parser.
Languages are generally specified with a hierarchical grammar. This better
decouples the specification from the implementation.
The SLK Parser Generator: www.slkpg.com
Return to the
comp.compilers page.
Search the
comp.compilers archives again.