I'm interested in using the CLASSPATH libraries in combination with several VMs, and am sure that as I read the code I'll have questions or comments on implementation. However, a great effort seems to have been expended to be anal about legal issues, so I'd like to know what I cannot say on the mailing list to avoid polluting it. I've read portions of Sun's JDK source code and have signed their non-commercial use license. I've used mocha to decompile portions of the javax packages that don't come with source. I've read sections of the internals of swing. Of course I've also read chunks of Kaffe and Japhar, but presumably that's OK. Can I: - point out bugs in the existing classpath code so that someone else could correct them? If I do this, should I avoid including "fixed" code? - point out errors in the documentation in classpath? - suggest ways of designing classpath for improved portability? thanks alex
