eonard <andrew_m_leon...@uk.ibm.com>
Cc: core-libs-dev@openjdk.java.net
Date: 09/04/2018 19:52
Subject: Re: RFR: Export InitializeEncoding for JVM access
Hi Andrew,
ok, it turns out the prototype in jni_util.h also needs to be updated to
be consistent for Windows and Solaris.
And
4/2018 15:39
Subject: Re: RFR: Export InitializeEncoding for JVM access
Hi Andrew,
Would it be sufficient to export the InitializeEncoding entry point?
Introducing a JNU_xx name may imply a level of support that is
unwar
, external: 01962 815913
internet email: andrew_m_leon...@uk.ibm.com
From: Roger Riggs <roger.ri...@oracle.com>
To: Andrew Leonard <andrew_m_leon...@uk.ibm.com>
Cc: core-libs-dev@openjdk.java.net
Date: 06/04/2018 15:39
Subject: Re: RFR: Export InitializeEncoding fo
Hi Andrew,
Would it be sufficient to export the InitializeEncoding entry point?
Introducing a JNU_xx name may imply a level of support that is
unwarranted since
it is part of system initialization and may change as needed by the
implementation.
Simply exporting it would put it on par with
Hi Roger,
The OpenJ9 VM implementation provides its own java.lang.System, which
performs similar type early-on VM initialization to the OpenJDK core
library classes. The basic reason for invoking the method is to initialize
the platform encoding either called from a related core library method,
Hi Andrew,
The function itself seems straightforward enough.
Can you clarify the boundary that you are replacing? The initialization
has a lot of
intermingled responsibilities and is quite sensitive.
What else needs to be said about when it can be called and who should be
calling it?
I
Hi,
I would like to propose and find a sponsor for this change please, which
is is export from libjava the JNU_InitializeEncoding() method, so that a
JVM can initialize the platform encoding. Currently
Java_java_lang_System_initProperties initializes the encoding, however for
a generic JVM
