[ 
https://issues.apache.org/jira/browse/GROOVY-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560064#comment-14560064
 ] 

Paul King edited comment on GROOVY-7435 at 5/26/15 11:08 PM:
-------------------------------------------------------------

Not related to the Groovy issue per se but out of curiosity google translate 
says the symbol means "Object". Is that correct? And is this symbol info 
correct:
{noformat}
Unicode character,Oct,Dec,Hex,HTML
对 cjk unified ideograph 5bf9 055771 23545 0x5BF9 对 
象 cjk unified ideograph 8c61 0106141 35937 0x8C61 象 
{noformat}



was (Author: paulk):
Not related to the Groovy issue per se but out of curiosity google translate 
says the symbol means "Object". Is that correct?

> Compilation failure when using non-ASCII chars as method return type
> --------------------------------------------------------------------
>
>                 Key: GROOVY-7435
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7435
>             Project: Groovy
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 2.1.6, 2.4.3
>            Reporter: Rodolfo Cruz
>            Priority: Critical
>         Attachments: InternationalizationTest.groovy
>
>
> When trying to declare the return type of a method having non-ASCII 
> characters, such as in the following example:
> {code:title=InternationalizationTest.groovy|borderStyle=solid}
> @groovy.transform.ThreadInterrupt
> @groovy.transform.TypeChecked
> public class 对象 {
> public 对象 get对象()
> {
>     return new 对象()
> }
> }
> def myVar = new 对象()
> {code}
> the compilation fails with the message:
> {{unexpected token: public at line: 6, column: 1}}
> Those characters are valid according to the [official 
> documentation|http://docs.groovy-lang.org/latest/html/documentation/#_identifiers]
>  and using them in other places such as a class or variable declaration works 
> as expected.
> I'm attaching the example in order to provide an easy way to test the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to