JDK-4884881 : use non-identifier character in synthetic names
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_8
  • CPU: generic
  • Submitted: 2003-06-27
  • Updated: 2017-05-16
  • Resolved: 2003-08-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Related Reports
Relates :  
JDK-4923163 - NullPointerException thrown in ClassDoc.superclassType()
Relates :  
JDK-4972569 - REGRESSION:java.awt.Component.AccessibleAWTComponent changed its serialVersionUI
Relates :  
JDK-4996984 - REGRESSION: api/java_applet/Applet/AccessibleApplet/serial/index.html#Input
Description
When javac generates synthetic names, it should draw them from the set
of identifiers that users can't use.  In 1.5, the VM spec allows the use
of most unicode characters in identifiers, even though those characters
aren't accepted in Java programs.

For example, instead of using names like this$0 and val$xyzzy, we could
name the synthetics this#0 and val#xyzzy.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b16
14-06-2004
PUBLIC COMMENTS javac now uses "+" instead of "$" in many synthetic identifiers when you specify -target 1.5. ###@###.### 2004-01-22
22-01-2004
EVALUATION We've long wanted to do this. Now its possible. ###@###.### 2003-06-26
26-06-2003