> From: Brian Jones
> Subject: Re: Excellent News About java.io
>
> "Aaron M. Renn" <[EMAIL PROTECTED]> writes:
> >
> > 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.
>
> I think we need to nail down what we are using, JCL/NSA/others, and
> document it in the hacking texinfo file.
>
Agreed.
> <snip>
>
> > 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.
>
> John should be posting a second, more usable patch, to the ftp site
> soon.
Soon enough, anyway ... I've got Thread and Class integrated again, this
time using NSA, and I'm working on the other stuff. Constructor is really
the only other thing that needs it. I'm running into build problems (cannot
find jni.h) right now.
> He has also posted to the website information on getting
> Classpath to work with a virtual machine in general. This should be
> helpful to anyone wanting to get us working with Kaffe. Takers?
>
About that document ... it's got a few rather obvious formatting errors, but
besides that, there are a number of things I gleaned when I began
investigating a 1.2 java.lang. Those things (like having the VM notify
Classpath when it creates a class in a given ClassLoader) are not necessary
just yet.
I think as soon as the first release is out the door we should work on
finishing up java.security and a 1.2 java.lang. That would make a nice
second release, along with (hopefully) AWT. Ever closer to the 1.2 spec.
--John Keiser
