-
Notifications
You must be signed in to change notification settings - Fork 770
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
Incremental parsing doesn't work with unquoted stuff when JSMN_STRICT is not defined #179
Comments
The problem here is mostly the way non-strict mode is. There is no definition of how it works and so it's difficult to say if behaviour is expected or not. Because of that, non-strict mode will be most likely dropped in a future release. In case it's still needed, a proper definition is required. You are welcome to give your input at #159. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is a small program that shows the problem:
This will see unquoted characters be turned into individual tokens:
The output for non-incremental or strict is correct:
Obviously it's hard for the parser to detect the expected end for unquoted numbers. The solution could be to append to the previous token if it's a primitive and there has been no intervening space.
The text was updated successfully, but these errors were encountered: