[Stuart D. Gathman]
> The main Jython package is 100% Java. That is an important feature.
> The Java platform has no readline equivalent (or any decent console
> I/O for that matter on which a Java readline could be built).
> As a result, readline for Java is necessarily a JNI extension and is
> platform specific. The best you can ask for is the 100% Java Jython
> you have now, plus RPMs/InstallEXEs/Whatever for various JNI extensions
> on selected popular platforms.
Thank you Stuart, for explaining it so clearly.
> Perhaps the jython.org page should have
> a spot for Jython JNI modules for various platforms (it currently has
> a list of major JVMs for various platforms). Users can contribute
> RPMs/Whatever or links to same.
If a user actually takes on the task of compiling and integrating
readline (while still honoring the GPL license <wink>), I will gladly
add a link to the RPM. So far it haven't happened and I don't need it
myself since I'm using win2k.
> The major JNI modules currently popular are
> jnios more posix os features
> readline history editing for console input
> On a different but related note - I am very grateful for the continuing
> JDK 1.1 runtime compatibility.
Be assured that jdk1.1 support will continue as long as I carry any
weight. I also depend on it.
> We have a handful of clients on JDK 1.1.6
> for AIX4.1 that are not interested in upgrading since everything is working
> fine. (Upgrading requires replacing hardware and OS - IBM provides Java2
> on AIX >= 4.3 only.) The fact that it won't build on 1.1 is not a problem - we
> can run Java 2 on our development machines.
That sounds like a bug. Ideally the ant build script should detect the
JDK used when compiling and skip all the java2 classes. I haven't tried
it for a while, so it may have broken in the current CVS. A bugreport
will be appreciated. A patch to build.xml will be appreciated even more