I have started the coding spree I said I was going to go on. I think
java.io is ready for our first release. I have made the following changes:
-- Fixed broken HTML in javadocs
-- Updated for complete Java 1.2RC2 spec conformance (excepting
serialization (Geoff Berry's baby) and a couple items I felt
absolutely had to be included despite non-conformance)
-- Fixed a couple of bugs
-- Re-ran all tests with the latest Japhar from CVS. Everything ok.
Some things remain untested. Nevertheless, all modules compile and the
basics seem to be working alright. Building things remains the big
problem. I am still compiling the Java by hand and the native code must be
hand linked.
John, you said you were using my java.io for your testing, but I highly
doubt that is the case. The native library build succeeds fine, but due to
a lack of interlibrary dependencies in libtool (possibly corrected now), it
crashes on an undefined symbol at runtime. Additionally, FileDescriptor had
a bug that was exposed by the latest Japhar which caused JVM symbol lookup
errors.
Another issue is that the native routines still use functions in John's JCL
common library that I don't know if we still are officially using. I'm
talking the method/field id caching and JCL_jstring_to_cstring.
If anybody wants to test with java.io, let me know and I'll put up a tarball
with compiled Java classes and instructions on how to build the native
code. (You need to link and install the native shared library by hand).
Next up, I need to get java.net in shape, then I'm going to focus on either
the build process or Japhar integration or whatever else needs help.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
