possible problem with JNI GetStringUTFChars

Alan Snyder javalists at cbfiddle.com
Mon Jan 28 22:15:51 UTC 2019

In case you missed my previous message, there is a use case for file paths using macOS APIs.


> On Jan 28, 2019, at 2:10 PM, Stuart Marks <stuart.marks at oracle.com> wrote:
> I think it would be far too troublesome to try to migrate the JNI methods to process real UTF-8 instead of modified UTF-8. That raises the question, though: is there a use case for processing real UTF-8 within JNI? For example, for interoperating with external components that expect real UTF-8. If so, perhaps some conversion methods could be added.

More information about the core-libs-dev mailing list