-
Notifications
You must be signed in to change notification settings - Fork 449
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
Jison no longer produces strict output #285
Comments
This is causing some rather annoying results, as it (for instance) does not allow me to use some ES6 code in io.js given that it requires strict mode. |
Any progress on this issue? For now it is impossible to use generated parser with Babel in strict mode. Blacklisting strict mode is not preferable solution here. |
Also having this with browserify. |
For the ones who need this badly: https://github.com/GerHobbelt/jison (jison used Esprima to tweak the core of the generated parsers, but it effed up the core and action code comments which help me to diag/debug grammars in the wild 👎 -- another @GerHobbelt feature where the grammar rule gets printed as a comment with the |
Seems to have been fixed in b9d5673 |
Aye, 0.4.16 has been published. Thanks y'all! |
Since d1d8ae9 jison has been producing code that contains:
I include the generated jison code within a "use strict" block. When loading this file with nodejs, I get the following error:
If I remove the "_token_stack:" label, the error disappears. Additionally, it seems the _token_stack label is not actually used in my generated file, so I'm unsure if it's safe to delete.
The text was updated successfully, but these errors were encountered: