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

Eric Milles commented on GROOVY-9712:
-------------------------------------

Another way of looking at this is that field/property uses the 
generalized-typename rule and a method's return type uses standard-typename 
rule.  The later requires a capital letter (A-Z) as the first name character.  
The former has allowances for lowercase names.  I'm not sure why this 
distinction exists in the parser.

{code}
generalClassOrInterfaceType
options { baseContext = classOrInterfaceType; }
    :   qualifiedClassName typeArguments?
    ;

standardClassOrInterfaceType
options { baseContext = classOrInterfaceType; }
    :   qualifiedStandardClassName typeArguments?
    ;
{code}

> groovyc fails when compiling class starting with unicode character
> ------------------------------------------------------------------
>
>                 Key: GROOVY-9712
>                 URL: https://issues.apache.org/jira/browse/GROOVY-9712
>             Project: Groovy
>          Issue Type: Bug
>          Components: Compiler
>    Affects Versions: 3.0.5
>         Environment: Windows 10 version 1809
> Groovy 3.0.5
>            Reporter: Ted Lundqvist
>            Assignee: Eric Milles
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
>  
> Compiling the code below with groovyc results in the following error message:
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
> failed:
>  Ö_ClassWithUlmaut.groovy: 2: Unexpected input: '(' @ line 2, column 41.
>  Ö_ClassWithUlmaut getInstance(){
>  ^
> 1 error
>  
> The file is encoded in Windows-1252 and I'm compiling it with the following 
> command:
>  \Tools\groovy-3.0.5\bin\groovyc --encoding Windows-1252 
> Ö_ClassWithUlmaut.groovy
> Compiling with version 2.5.8 works fine
>  
> The problem only seem to occur when the class name starts with a unicode 
> character i.e. the problem doesn't occur if the class name has an unicode in 
> it as long as it isn't the first character
> Example:
> {code:java}
> class Ö_ClassWithUlmaut {
>     static Ö_ClassWithUlmaut getInstance(){
>     }
> }
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to