John Leuner ([EMAIL PROTECTED]) wrote:
> I've started adapting a simple JVM that I'm working on to support
> Classpath. What I've seen of Classpath so far is very impressive and I'm
> keen to convert from the old classlib stuff I was using (mostly from Sun,
> writing the native methods myself where necessary).
Thanks for the comments.
> I'm having some problems with Strings though, in particular the Encoder
> setup. As yet I don't have support for reflection and the Constructor
> class. So what I'ld like to do is just hardwire a default en/decoder for
> all Strings. My initial attempts at doing this with Encoder8859_1 seem to
> work, but it doesn't format newlines correctly.
>
> I don't know enough about these Encoders to know exactly what I should be
> using, what is the 'default' conversion from Characters to bytes?
Yes, just modify gnu.java.io.EncodingManager to hard load the encoder
class you want. By default, this basically translates bytes straight
through to chars by appending a 0 high bytes. Newlines problems are
likely caused by something else. What exactly is happening?
> I'ld appreciate any advice. Are there any other projects besides Japhar
> using Classpath?
JOS is planning on using Classpath, I believe. Right now we are just
so developmental that it is hard to be useful to other projects. I'm
hoping that this changes over the next few months as AWT gets done,
we incorporate RMI, and then we can just focus on stability, bug fixes,
and performance.
Definitely keep us posted on your progress. John Kieser did a lot of
the world developing the interface layer between the VM and Classpath.
I did some work on that as well. So if you get stuck, I can try to
help you out. Most things are pretty self contained though.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
