You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why is the lexer swallowing the trailing bracket when there is no space between the content and the surrounding brackets?. This looks like a bug to me. It has something to do with second character class in the content regex ([^ ]*), when I change that to also not match ) it works.
The text was updated successfully, but these errors were encountered:
databus23
changed the title
strange flexing behavior
strange lexing behavior
Oct 16, 2015
#16 mentions requiring a newline at the end of the file. This looks to apply here too. Adding even a space at the end matched the last bracket correctly "(rule) "
I'm having a hard time understanding the behavior of the lexer in the following case:
Output of nex -r -s huh.nex:
Why is the lexer swallowing the trailing bracket when there is no space between the content and the surrounding brackets?. This looks like a bug to me. It has something to do with second character class in the content regex (
[^ ]*
), when I change that to also not match)
it works.The text was updated successfully, but these errors were encountered: