Proposal: make gcjh default to JNI mode
Bryce McKinlay
mckinlay@redhat.com
Thu Apr 28 16:09:00 GMT 2005
Andrew Haley wrote:
>Thomas Fitzsimmons writes:
> > > Currently gcjh defaults to emitting CNI headers. I propose we change it
> > > to emit JNI headers by default. That way gcjh will become command-line
> > > compatible with javah. This would allow me to remove the javah wrapper
> > > script from java-gcj-compat and instead symlink javah directly to gcjh.
> >
> > I should have mentioned; I'm proposing this change for mainline (4.1),
> > not 4.0.x.
>>I think this is an awful idea. CNI is our preferred route and offers
>many advantages. To change gcjh to emitting JNI headers by default
>would send out an inapporpriate message. If you would like gcjh to
>look at its argv[0] and do something different when invoked as javah I
>wouldn't object.
>I agree. Despite the fact that "downgrading" CNI is not the direction we
want to take, dramatically changing the behavior of an existing tool is
a no-no and would contradict/break all the documentation, FAQs,
Makefiles etc that are out there.
On the other hand, using JNI by default if invoked as "javac" seems like
a great idea!
Bryce
More information about the Java
mailing list