JDK-4218179 : JNI name mangling rules should specify lower- or uppper-case Unicode
  • Type: Bug
  • Component: docs
  • Sub-Component: guides
  • Affected Version: 1.2.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1999-03-08
  • Updated: 2014-04-02
  • Resolved: 2004-02-16
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 beta2Fixed
Related Reports
Relates :  
JDK-6462398 - jni spec should specify which characters are unicode-escaped when mangling
Description

Name: krT82822			Date: 03/08/99


The name-mangling rules in the JNI specification do not state
whether the string used for Unicode characters
should be lower- or upper-case; e.g.,
_0abcd versus _0ABCD.  The case matters for most tools.
(Review ID: 54039)
======================================================================
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-beta2
14-06-2004
EVALUATION Sheng shouldn't we codify this in the JNI spec? anand.palaniswamy@Eng 1999-03-22 Steffen, while I was cleaning up I found a few bugs that had to be dealt with. mohammad.gharahgouzloo@Eng 2000-04-21 ###@###.### 2003-11-04 The hotspot JVM will generate lower case characters for hexidecimal representations of non-ASCII Unicode characters in native method names. This table or its successor should be updated: http://webwork.sfbay/j2se/1.4.2/docs/guide/jni/spec/design.html#wp133
11-06-2004
PUBLIC COMMENTS Table 2-1 has been updated. ###@###.### 2004-02-16
16-02-2004