This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: JNI without Jni_Lookup() ?

From: Tom Tromey <tromey at redhat dot com>
To: Erik Poupaert <erik dot poupaert at skynet dot be>
Cc: gnustuff at thisiscool dot com, java at gcc dot gnu dot org
Date: 19 Apr 2004 15:19:17 -0600
Subject: Re: JNI without Jni_Lookup() ?
References: <TSOI82FAE9FEA8B9RN87E0M3ZVQID65.408328e3@p733><87oepnnawa.fsf@fleche.redhat.com><20040419201705.49cb7884.erik.poupaert@skynet.be>
Reply-to: tromey at redhat dot com

>>>>> "Erik" == Erik Poupaert <erik.poupaert@skynet.be> writes:

>> It would be pretty helpful if we had a tool that could check this sort
>> of thing at build time. 

Erik> The linker does that automatically, but only if you ...
Erik> link statically.

Yeah, but this won't work for JNI.  One of the problems with JNI is
that every method has two possible manglings.  You can't know until
runtime which is the one to use (unless you design some way to tell
gcj about it ahead of time).  So, add that to the other reasons that
this approach won't really work...

Tom

Follow-Ups:
- Re: JNI without Jni_Lookup() ?
  - From: Erik Poupaert
- Re: JNI without Jni_Lookup() ?
  - From: Erik Poupaert

References:
- Re: JNI without Jni_Lookup() ?
  - From: Mohan Embar
- Re: JNI without Jni_Lookup() ?
  - From: Tom Tromey
- Re: JNI without Jni_Lookup() ?
  - From: Erik Poupaert

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]