-
Notifications
You must be signed in to change notification settings - Fork 4
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Parser does not work when compiling to JavaScript #84
Comments
Sorry, nimly does not support compiling to JS now. nimly targets to use as a part of compilers, so it only targets C/C++ compiling. In what situation do you want to use nimly in JS? If it looks like a common situation, I will try to support JS. Or, you are very welcome to make PRs for supporting JS! |
I'm making a library that my team wants to use both in JavaScript and in Python. But I found out that I can use NPeg instead (which seems to work fine with JavaScript), so it's not a problem in the end. Thanks! |
Minimal example:
When the code is compiled to C, it successfully outputs
0
. However, if compiled to JavaScript (with-d:release
), it outputs:Note that this happens both in Node and in the browser. The error happens on the first token passed to the parser, no matter what the parser looks like.
The text was updated successfully, but these errors were encountered: