Proposal: make gcjh default to JNI mode

[Bryce McKinlay]

Thomas Fitzsimmons wrote:

>> > We can't just call the separate tool "javah" because that will conflict
>> > with proprietary versions of "javah".  For example, we had problems when
>> > fastjar was installed as /usr/bin/jar.  So I propose calling it
>> > "gcjhjni" and installing it in $prefix/bin alongside gcjh.  Then I can
>> > create a direct symlink from javah -> gcjhjni in java-gcj-compat.
>>
>>I hate that name.  gnujavah is surely better, but any pronouncable
>>name is OK with me.
>>
>>    
>>
>
>Since we don't like having "java" in our names, and since Andrew and I
>proposed "gjnih" simultaneously on IRC, we'll go with "gjnih" unless
>anyone objects.
>  
>
Might gcj-jnih be better? I kinda like the idea of prefixing our tools 
with "gcj-", ala gcj-dbtool. It would be convenient for a gcj novice to 
be able to type "gcj" in bash and then hit tab and get a list of all the 
tools. Having said that, we already have some tools that just start with 
g - eg grimc.

Bryce