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 2018/06/23 07:00:04 UTC

[jira] [Updated] (GROOVY-8662) support full unicode capabilities from antlr2 parser in antlr4

     [ https://issues.apache.org/jira/browse/GROOVY-8662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King updated GROOVY-8662:
------------------------------
    Component/s: parser-antlr4

> support full unicode capabilities from antlr2 parser in antlr4
> --------------------------------------------------------------
>
>                 Key: GROOVY-8662
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8662
>             Project: Groovy
>          Issue Type: Improvement
>          Components: parser-antlr4
>            Reporter: Paul King
>            Priority: Minor
>
> The Antlr2 parser allows the entire source code to be entered as unicode characters, e.g. see
> {{groovy.EscapedUnicodeTest}}. For the Antlr4 parser, for efficiency reasons, this was limited to names, e.g. class names and variable names etc. The thinking at the time was that the full use of unicode was a very special use case that didn't warrant the performance hit.
> We could however, optionally run a pre-parser (enabled by some command-line switch perhaps). Doing so would cause inaccuracies however in node position information - since the pre-parser would alter the file during unicode processing.
> We regard such functionality as low priority but include this issue to document our thinking about the preferred approach if such functionality was introduced.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)