FULL PRODUCT VERSION :
build 1.7.0-ea-b130
ADDITIONAL OS VERSION INFORMATION :
Windows7 SP1 64bit
A DESCRIPTION OF THE PROBLEM :
I checked the result of
Character.isJavaIdentifierPart('\u30fb').
On JDK6 it is true,
but on JDK7 it is false.
So Eclipse Java editor marks the charcter as 'Invalid Character'
when it runs on JDK7.
And you can't compile the class using this character as JavaIdentifierPart on JDK7.
REGRESSION. Last worked in version 6
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Create a class
2. In the class, print the result of this method
System.out.println( Character.isJavaIdentifierPart('\u30fb') );
3. Compile and run it on JDK6.
4. Compile and run it on JDK7.
5. See
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I expect Step 4. shows 'true'
ACTUAL -
Step4. shows 'false'
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Not use this character.
But I can't know which characters should I avoid.
build 1.7.0-ea-b130
ADDITIONAL OS VERSION INFORMATION :
Windows7 SP1 64bit
A DESCRIPTION OF THE PROBLEM :
I checked the result of
Character.isJavaIdentifierPart('\u30fb').
On JDK6 it is true,
but on JDK7 it is false.
So Eclipse Java editor marks the charcter as 'Invalid Character'
when it runs on JDK7.
And you can't compile the class using this character as JavaIdentifierPart on JDK7.
REGRESSION. Last worked in version 6
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Create a class
2. In the class, print the result of this method
System.out.println( Character.isJavaIdentifierPart('\u30fb') );
3. Compile and run it on JDK6.
4. Compile and run it on JDK7.
5. See
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I expect Step 4. shows 'true'
ACTUAL -
Step4. shows 'false'
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Not use this character.
But I can't know which characters should I avoid.
- duplicates
-
JDK-6990687 Character.isJava/UnicodeIdentifierStart/Part() should be stable over Unicode versions
-
- Closed
-