[
https://issues.apache.org/jira/browse/GROOVY-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952301#comment-15952301
]
Daniel Sun commented on GROOVY-8131:
------------------------------------
bq. Anyway... I think this kind of bug can be fixed in the antlr grammar
Jochen, I think the new parser Parrot can be refined to support some code like
{code}
def a
= 1 + 2
{code}
but I am not going to make Parrot support
{code}
def a = 1
+ 2
{code}
In other words, the first token in second line should be invalid for the
statement.
> Statement continued onto next line is flagged when first character is "="
> -------------------------------------------------------------------------
>
> Key: GROOVY-8131
> URL: https://issues.apache.org/jira/browse/GROOVY-8131
> Project: Groovy
> Issue Type: Bug
> Components: Compiler
> Affects Versions: 2.4.5
> Environment: Ubuntu Linux
> `uname -a`:
> Linux biostar 4.4.0-69-generic #90-Ubuntu SMP Thu Mar 16 16:52:31 UTC 2017
> x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Richard Elkins
> Priority: Minor
> Attachments: grbug.java
>
>
> Source code attached (grbug.java).
> `javac` v8 compiles variable declarations s1, s2, and s3 successfully.
> `groovyc` flags s3:
> "unexpected token: = @ line 9, column 3."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
