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 2020/01/27 10:53:00 UTC

[jira] [Updated] (GROOVY-2857) Full support for special characters in method names

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

Paul King updated GROOVY-2857:
------------------------------
    Fix Version/s:     (was: 3.x)

> Full support for special characters in method names
> ---------------------------------------------------
>
>                 Key: GROOVY-2857
>                 URL: https://issues.apache.org/jira/browse/GROOVY-2857
>             Project: Groovy
>          Issue Type: Improvement
>          Components: Compiler
>    Affects Versions: 1.6-beta-2
>         Environment: Mac OS 10.5.2
> JDK 1.5.0_13
> Groovy 1.6-beta-2-SNAPSHOT
>            Reporter: Peter Niederwieser
>            Priority: Major
>
> Groovy allows method names to be specified as String literals. This enables the use of special characters in method names, such as space, comma, and question mark. However, when such a name become part of a class name, a "java.lang.ClassFormatError: Illegal class name" is thrown at runtime. As far as I can tell, this happens when: 
> 1. closures are involved 
> 2. the new call site mechanism generates a class on-the-fly 
> To fully support special characters in method names, the naming scheme of generated classes should thus be adapted. Also, the (few) characters that aren't allowed to appear in a method name according to the JVM specification should be rejected by the parser. For more information and related discussion see:
> http://groups.google.com/group/jvm-languages/browse_thread/thread/c5c9c0bafe1ef0c8
> http://www.nabble.com/In-Love-with-Groovy-tt17240709.html



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