libgcj/117: _Jv_PthreadCheckMonitor test is not portable.

Tom Tromey tromey@cygnus.com
Fri Dec 10 08:00:00 GMT 1999


>>>>> "Joerg" == Joerg Brunsmann <joerg.brunsmann@FernUni-Hagen.de> writes:

Joerg> I can't argue technically but I argue with: why bother if
Joerg> someone else has already gone through the pain. For alternative
Joerg> OS thread layer see GLib and NSPR:
Joerg> http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&dir=glib/gthread &
gthread sucks in glib, which we definitely don't want. It is just
bloat for us.
Joerg> http://lxr.mozilla.org/seamonkey/source/nsprpub/
My understanding is that this is a thread system and does not use
native threads. This is also not what we want. (Maybe I'm wrong.
The URL you give is hardly an easy way to find out...).
Anyway, having control over the thread layer is important to us, I
think. We want to be able to write new thread ports without having to
mess around (with negotiations or forking other people's packages).
T


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /