Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upparser doesn't handle expressions vs statements properly. #137
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Yeap, looks like a lexing issue. Will make a priority to fix. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
tef
Oct 23, 2012
iirc, in parse.y this is handled by the use of LPAREN/LPAREN_ARG, which is controlled by the lexer state hack EXPR_*
tef
commented
Oct 23, 2012
|
iirc, in parse.y this is handled by the use of LPAREN/LPAREN_ARG, which is controlled by the lexer state hack EXPR_* |
ghost
assigned
adambeynon
Oct 23, 2012
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This should now be fixed on master, by 13ed3c5. |
adambeynon
closed this
Oct 27, 2012
ghost
referenced this issue
Aug 22, 2013
Closed
opal-parser doesn't handle array dereferences vs array literals properly #145
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tef commentedOct 20, 2012
In ruby,
meth (args).meth2 {block}parses differently tometh(args).meth2 {block}. The whitespace is significant.For example, in opal, this prints [1], [1], rather than [2], [1] as expected