JDK-6990687 : Character.isJava/UnicodeIdentifierStart/Part() should be stable over Unicode versions
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Future Project
  • OS: generic,windows_7
  • CPU: generic,x86
  • Submitted: 2010-10-08
  • Updated: 2011-03-08
  • Resolved: 2011-02-04
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.
JDK 8
8Resolved
Related Reports
Duplicate :  
Description
This was raised in the locale-enhancement OpenJDK project mailing list. Here is the excerpt:

---
Unicode has mechanisms to guarantee that program identifiers are stable over versions of Unicode, and defines properties that have that guarantee: XID_Start and XID_Continue (see
http://unicode.org/reports/tr31/).

However, when I look at the documentation for isJavaIdentifierPart,
isCharacteIdentifierPart, etc., it appears that these are defined not in
terms of those properties, but in terms of properties that are *not*
stable over releases.

http://download.oracle.com/javase/6/docs/api/java/lang/Character.html#isJavaIdentifierPart(int)
etc.

That means that a program that was compiled under one release of Java
could fail under a future one, simply because the identifiers break
under the new release.
---

The entire email thread can be found at http://mail.openjdk.java.net/pipermail/locale-enhancement-dev/2010-October/000284.html

Comments
EVALUATION XID_Continue isn't stable. U+30FB and U+FF65 in Unicode 4.0.0 were removed in Unicode 4.1.0.
08-03-2011