Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compilers > #1713 > unrolled thread
| Started by | "SLK Mail" <slkpg4@gmail.com> |
|---|---|
| First post | 2016-06-07 08:53 -0800 |
| Last post | 2016-06-07 08:53 -0800 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.compilers
precedences vs. hierarchy "SLK Mail" <slkpg4@gmail.com> - 2016-06-07 08:53 -0800
| From | "SLK Mail" <slkpg4@gmail.com> |
|---|---|
| Date | 2016-06-07 08:53 -0800 |
| Subject | precedences vs. hierarchy |
| Message-ID | <16-06-007@comp.compilers> |
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
Back to top | Article view | comp.compilers
csiph-web