How would people feel about moving the japhar sources over to using NSPR
exclusively? The original purpose of NSPR was to make porting
netscape's java implementation across all the platforms navigator runs
on. It can be configured to use pthreads, cthreads, beos's threads,
windows's threads, as well as its own user-space threads. By using it,
we can also remove many of the #ifdefs we have in our native code, and
clean up the mess of types we have in libruntime (u2, uint32_t, etc.)
Also, arch/ could more or less go away entirely.
It also has portable (if not totally optimized) string functions, hash
tables (which are much more efficient than our paltry class-repository
code :)
The only overlap between nspr and our current code that couldn't be
resolved simply by using nspr's version is the libtool stuff. I don't
see this as a great hardship, and since the libltdl code is so small,
bloat isn't a problem either.
It would entail having another dependency, but we could always import
the nspr sources periodically and include then in the distribution.
Chris
