You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/02/01 23:19:04 UTC
[jira] [Closed] (GROOVY-7958) Incorrect parsing of comma-separated
variable declaration as single statement after if/while/for
[ https://issues.apache.org/jira/browse/GROOVY-7958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King closed GROOVY-7958.
-----------------------------
> Incorrect parsing of comma-separated variable declaration as single statement after if/while/for
> ------------------------------------------------------------------------------------------------
>
> Key: GROOVY-7958
> URL: https://issues.apache.org/jira/browse/GROOVY-7958
> Project: Groovy
> Issue Type: Bug
> Reporter: Paul King
> Assignee: Paul King
> Fix For: 2.4.8
>
>
> Currently during parsing a single (comma-separated) variable declaration is turned into multiple statements on the fly. If this occurs when such a statement is the single statement after an if/while/for, then only the first statement is picked up and the next is left dangling within the AST tree. For 'if' it becomes the else statement! while in the 'for/while' cases I think it is ignored. So, the following code doesn't work as expected:
> {code}
> int xNext = 0, yNext = 0
> if (false) int x = xNext++, y = yNext++
> assert xNext == 0 && yNext == 0
> if (true) int x = xNext++, y = yNext++
> assert xNext == 1 && yNext == 1
> {code}
> This is very much an edge case (what good is a declaration if you then have no block in which to use it?) but is still worth fixing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)