Re: New classes from Classpath

[Mark Wielaard <mark at klomp dot org>]

Hi,

On Mon, Oct 01, 2001 at 03:36:55PM -0600, Tom Tromey wrote:
> One question for all libgcj hackers: how far into JDK 1.4 do we want
> to go?  We already have a little piece (IdentityHashMap, since it was
> useful for JNI).  Do we want CharSequence?  Some Classpath hackers
> seem to be working on 1.4 compatibility even though it hasn't been
> released yet.

The 1.4 api has some nice new features such as java.util.prefs and
chaining support for Throwable which I am also working on. I implemented
CharSequence just for fun when I was exploring the new java.util.regex
package (which I am not working on). I think it is a good thing to try
to track the standard so we might find design issues for which we could
file bug reports. I don't mind tracking any future changes for the 1.4
things I introduce and fix them when the standard changes.

> The only potential problem is in Thread.java:
> [...]
> I actually have a similar patch in a tree here.  In my patch I call
> InheritableThreadLocal.newChildThread() from the `current != null' branch
> of the `if' statement in the Thread constructor.  Otherwise I think
> you run into problems because InheritableThreadLocal will look at the
> currently executing thread -- which during startup might be null.
> Also it doesn't seem important to try to inherit these objects for
> the initial thread anyway.  What do you think of this?

I think you are right and you might have found one of the problems that
I was having with some small tests that I was running. There is also
another problem since one test throws a ConcurrentModificationExceptions
from newChildThread(). Seems that I have a thinko somewhere in the code
but I cannot find it. Will debug some more tomorrow.

Cheers,

Mark
-- 
Stuff to read:
    <http://www.toad.com/gnu/whatswrong.html>
  What's Wrong with Copy Protection, by John Gilmore