This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: do we need separate thread for FirstThread
- To: Per Bothner <per at bothner dot com>
- Subject: Re: do we need separate thread for FirstThread
- From: Tom Tromey <tromey at redhat dot com>
- Date: 08 Feb 2001 17:55:34 -0700
- Cc: java at gcc dot gnu dot org
- References: <m21yt8exes.fsf@kelso.bothner.com>
- Reply-To: tromey at redhat dot com
>>>>> "Per" == Per Bothner <per@bothner.com> writes:
Per> The last I think is the killer argument, but the other ones are
Per> also worth noting. So what are the arguments in favor of starting
Per> a separate native thread? Uniform representation for all Java
Per> threads? But we have to treat FirstThread special anyway, at
Per> least when we start it up.
I've been planning to make this change whenever I get around to it.
The idea is to write a "CNI Invocation API" and then rewrite the JNI
Invocation API on top of it.
Tom