RFR [XS] JDK-6462398: jni spec should specify which characters are unicode-escaped when mangling

Daniel D. Daugherty daniel.daugherty at oracle.com
Fri Apr 25 19:59:00 UTC 2014


Thumbs up.

Dan


On 4/25/14 9:17 AM, David Simms wrote:
> JDK-6462398 <https://bugs.openjdk.java.net/browse/JDK-6462398>: jni 
> spec should specify which characters are unicode-escaped when mangling
>
> Minor change to the JNI Specification 
> <http://docs.oracle.com/javase/8/docs/technotes/guides/jni/spec/jniTOC.html>:
>
> The section "Resolving Native Method Names 
> <http://docs.oracle.com/javase/8/docs/technotes/guides/jni/spec/design.html#resolving_native_method_names>" 
> should be slightly more specific in describing how characters are 
> mangled.
>
> Web review here: http://cr.openjdk.java.net/~dsimms/jnispec/6462398/ 
> <http://cr.openjdk.java.net/%7Edsimms/jnispec/6462398/>
>
> *Old Text*
>     *New Text*
> Unicode Character TranslationEscape Sequence     Denotes
> |_0XXXX|     a Unicode character|XXXX|. Note that lower case is used 
> to represent non-ASCII Unicode characters, for example,|_0abcd|as 
> opposed to|_0ABCD|.
>
>
>
> Unicode Character TranslationEscape Sequence     Denotes
> |_0xxxx|     a Unicode character|xxxx|, representing characters other 
> than ASCII alphanumeric ([A-Za-z0-9]). Note that lower case is used, 
> for example,|_0abcd|as opposed to|_0ABCD|.
>
>



More information about the hotspot-dev mailing list