-
Notifications
You must be signed in to change notification settings - Fork 1
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
LEXER: sign before POUND char like [-#"a"] is not recognized as a word and is misinterpreted #2319
Comments
Ren-C throws an error (but I prefer result like in Red)
|
Oldes
changed the title
LEXER fails in cases like: [-#"a"]
LEXER: sign before POUND char like [-#"a"] is not recognized as a word and is misinterpreted
Sep 4, 2018
Related issues:
|
Fixed in commit: Oldes/Rebol3@1a4c3a6 |
Oldes
referenced
this issue
in Oldes/Rebol3
Sep 4, 2018
…recognized as a word and is misinterpreted Before this fix: ``` >> [-#"a"] == [#"^""] >> [-#[none]] == [none] >> [-#{AA}] ** Syntax error: invalid "binary" -- "-#{AA}" ** Near: (line 1) [-#{AA}] ``` Now: ``` >> [-#"a"] == [- #"a"] >> [-#{AA}] == [- #{AA}] >> [-#[none]] == [- none] ```
With the above fix it is consistent with cases like:
|
Oldes
added a commit
to Oldes/Rebol3
that referenced
this issue
Sep 4, 2018
Here is another case which was fixed now:
Now:
|
Oldes
added a commit
to Oldes/Rebol3
that referenced
this issue
Sep 4, 2018
Oldes
added a commit
to Oldes/Rebol3
that referenced
this issue
Sep 4, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behaviour
In Rebol2 it is also wrong, but with different result:
Expected behaviour (like in Red)
Because I want to be able to write more compact charsets:
versus
The text was updated successfully, but these errors were encountered: