-
Notifications
You must be signed in to change notification settings - Fork 37
new Parser, missing lex #90
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
Comments
Hi @Mike-3, thanks for the praise, always great to hear from users! 😄 You're right, the new parser does not expose the tokens (intermediate representation) of the parsed expression in any way. This is due to this implementation relying on I considered the lexer an internal implementation detail of the parser, so have not maintained any sort of backwards compatibility there. However I'm curious to hear what your use case is? |
In this case, I used it for a verbal arithmetic solver and used the functionality to determine the available variables. But I'm sure I can do that some other way. |
That makes sense. I was planning to implement #73 soon which would solve that particular issue. |
Is there an alternative for the lex function in the new parser? I couldn't find anything suitable?
Great library. Thanks for expanding the functionality. It's also super fast.
The text was updated successfully, but these errors were encountered: