On 13/04/2017 10:30 AM, Iain Buclaw via Digitalmars-d wrote:
On 13 April 2017 at 10:12, Russel Winder via Digitalmars-d
<digitalmars-d@puremagic.com> wrote:
On Wed, 2017-04-12 at 10:59 +0100, rikki cattermole via Digitalmars-d
wrote:
[…]
Considering it was created in 2014, I think we're safe implementing
extern(JNI) support either which ways.
Although a little strange since nobody has completed a full JNI
implementation yet!
JNI will be around for decades because of the way deprecation works in
Javaland. I suspect though that if Charles gets the support of the JNA
folk to back his JNR basis for this proposal, it can all happen quite
quickly. JDK10 being possible though JDK11 more likely.
It may be of worthy note that gcc has dropped the Java frontend (gcj)
and thus the JNI from C/C++ in the compiler.
If JNI can work as a library, then there's no problem, however.
Tried as a library, not easy to get right, compiler would be a good deal
better.
