-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate 'optimal' lexers, i.e. the Need For Speed #20
Comments
GerHobbelt
added a commit
to GerHobbelt/jison-lex
that referenced
this issue
Jan 31, 2017
…t to deliver, the lexer *generator* will need information about which features are used, e.g. extended error handling, location tracking (with or without `yylloc.range` range tracking), etc.
GerHobbelt
added a commit
to GerHobbelt/jison-lex
that referenced
this issue
Mar 26, 2017
…thout it for the test grammars ATM; to be revisited later on when zaach#20 is addressed...
GerHobbelt
added a commit
to GerHobbelt/jison-lex
that referenced
this issue
Mar 26, 2017
GerHobbelt
added a commit
to GerHobbelt/jison-lex
that referenced
this issue
Mar 26, 2017
GerHobbelt
added a commit
to GerHobbelt/jison-lex
that referenced
this issue
Apr 8, 2017
… to the lexer compiler using better names, so they are confused once in there.
GerHobbelt
added a commit
to GerHobbelt/jison-lex
that referenced
this issue
Apr 8, 2017
…stics of the generated lexer to be used in the code optimizer.
GerHobbelt
added a commit
to GerHobbelt/jison
that referenced
this issue
Apr 8, 2017
…bits to the lexer compiler using better names, so they are confused once in there.
Compare with moo lexer: https://github.com/no-context/moo |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See also jison issue #341
The text was updated successfully, but these errors were encountered: