3 ms·
The paper: https://www.antlr.org/papers/allstar-techreport.pdf https://www.antlr.org/papers/allstar-techreport.pdf Has the important detail why it scored good
by acqq 7y ago
The paper:
https://www.antlr.org/papers/allstar-techreport.pdf https://www.antlr.org/papers/allstar-techreport.pdf
Has the important detail why it scored good in benchmarks against other parsers:
"7.3 Effect of lookahead DFA on performance
The lookahead DFA cache is critical to ALL(*) performance.
To demonstrate the cache’s effect on parsing speed, we disabled
the DFA and repeated our Java experiments. Consider the 3.73s
parse time from Figure 9 to reparse the Java corpus with pure
cache hits. With the lookahead DFA cache disabled completely,
the parser took 12 minutes (717.6s)."
I'd still most probably hand-roll, at least when making something for a long-term project, and not some "demo" -- there the stability and ease of maintenance is more important than fast availability of initial results.