Yup, semicolon insertion is the single biggest hurdle to creating a
grammar file for any of the stock parser generators.
Attila.
Sent from my ${mobile_handset_device}
On 2009.09.04., at 22:46, Norris Boyd <norrisb...@gmail.com> wrote:
And are you asking for a grammar in the sense of a LALR grammar that
can be used as input to a parser generator? We've always built a
custom lexer/parser in Rhino for a number of reasons (speed, handling
semicolon insertion, handling different versions of the language
within a single parser, etc
_______________________________________________
dev-tech-js-engine-rhino mailing list
dev-tech-js-engine-rhino@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
