-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
Regular expressions does not work #6
Comments
Thanks for trying this out @yisonPylkita ! Lexer We can prove this by looking at the token output for your source code, we end up with an
We would need to add some additional logic here to check for an expresion between the 2 Parser The error message could also be a bit more helpful too. |
Thanks for a quick replay. Woow, that is a quite detailed problem description. It will definitely help me with a PR. I will start working on this in coming week. |
@yisonPylkita how you getting on? |
@yisonPylkita work has happened on this here: |
Milestone has now been created for regular expressions so this can be closed: |
# This is the 1st commit message: The interpreter is now modular. # The commit message #2 will be skipped: # Moved array declarations to their own module # The commit message #3 will be skipped: # Added ArrowFunctionDecl # The commit message #4 will be skipped: # Removed the `Executor` trait, and added the `Assign` operator # The commit message #5 will be skipped: # Fixed documentation links # The commit message #6 will be skipped: # Added `BinOp` execution, and made operators `Copy`. # The commit message #7 will be skipped: # Moved `Node` executor to its own `Executable` implementation
Hi @jasonwilliams
Thank you for starting this project!
I tried to run this JS code
and got
The text was updated successfully, but these errors were encountered: