Re: encoder / decoder code

That sounds fine to me. I had once looked at what libgcj did noticed the great similarity between the two. One thing I would mention about what I wanted to accomplish with the Classpath implementation. I essentially wanted this to be useful as a charset conversion facility outside of the standa

Re: encoder / decoder code

Artur Biesiadowski ([EMAIL PROTECTED]) wrote: > > Both code bases take roughly the same approach. Only details differ. > > My recommendation is to take the libgcj framework, and then heavily > > modify it to incorporate the good points from Classpath: > > At some point in past Classpath converte

Re: encoder / decoder code

Artur> At some point in past Classpath converters were broken - they Artur> was using static variable in superclass in way presuming it Artur> will be different for each subclass. This allowed to have only Artur> one converter active at same moment (last one to initialize was Artur> overshadowing

Re: encoder / decoder code

Tom Tromey wrote: > Both code bases take roughly the same approach. Only details differ. > My recommendation is to take the libgcj framework, and then heavily > modify it to incorporate the good points from Classpath: At some point in past Classpath converters were broken - they was using stat

encoder / decoder code

I spent a little time recently looking at the character set conversion code in Classpath and libgcj. I don't have time to do the merge right now, but I thought I'd post my recommendations for posterity. Both code bases take roughly the same approach. Only details differ. My recommendation is to