You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Daniel Sun (JIRA)" <ji...@apache.org> on 2017/06/03 00:20:04 UTC
[jira] [Commented] (GROOVY-8210) Unicode escape sequence in string
literal yields incorrect source position
[ https://issues.apache.org/jira/browse/GROOVY-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035676#comment-16035676 ]
Daniel Sun commented on GROOVY-8210:
------------------------------------
Eric, have you tried the new parser Parrot? It doesn't rely on UnicodeEscapingReader to escape unicode, so I think the issue does not exist in Parrot.
> Unicode escape sequence in string literal yields incorrect source position
> --------------------------------------------------------------------------
>
> Key: GROOVY-8210
> URL: https://issues.apache.org/jira/browse/GROOVY-8210
> Project: Groovy
> Issue Type: Bug
> Reporter: Eric Milles
>
> This seems related to GROOVY-4378. If I enter {code}'\u0047'{code} into the Groovy Console and inspect the AST, I find the string literal's ConstantExpression has been assigned colums 6 to 9. A start position of 6 propagates to the parent return statement, block statement, etc. The start position should be column 1.
> I believe the UnicodeEscapingReader is stepping in front of the parser and so it never gets to process the original source characters '\', 'u', '0', '0', '4', '7'.
> Having incorrect source location for string literals such as this inhibits proper editing/refactoring in the IDE.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)