--SIyqsdZNHTcC3wfMYSp
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2006-11-24 at 10:39 +0900, M. Edward (Ed) Borasky wrote:
> Which "core libs"? The standard C implementation, jRuby or the Microsoft 
> CLR version? IIRC the jRuby team is going to or already is using the JVM 
> native threading model, and I have no idea what the Microsoft 
> implementors are doing, but I'm assuming they are building on the CLR 
> native threading model. And Ruby 1.9.x - 2.0 is supposedly going to use 
> native threads -- which presumably means at least Windows, Linux, MacOS 
> and Solaris. That pretty much leaves the 1.8.x C implementation.

That's about the shape of it.  Once fastthread's seen some decent use in
production, I'll turn it into a patch and submit it for hopeful
inclusion in the 1.8.x stdlib.

I hope that the implementation of the thread.rb primitives on the other
Ruby implementations will be taken care of eventually.  However, JRuby
uses the thread.rb from 1.8.x right now, which is kind of sad since
Thread.critical doesn't really work properly on JRuby.  I wouldn't be
surprised if the same were true of the other implementations.  Last I
looked, 1.9 was also more or less using a version of 1.8.x's thread.rb.

Frankly, the synchronization primitives in Ruby need a lot of help right
now on most or all of the implementations, and I'm trying to start the
ball rolling to get them fixed.

-mental

--SIyqsdZNHTcC3wfMYSp
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBFZnUNSuZBmZzm14ERAi6LAJwKAPwmcinh8QHWMDjUsiMDdM2FSQCfYoNp
cnuAkFK+rG4fBMmBDryixwor+
-----END PGP SIGNATURE-----

--SIyqsdZNHTcC3wfMYSp--