Fascinating... Is ruby native thread-friendly? Without the ability to 
keep multiple interpreter contexts, I would think this would cause the 
interpreter to go crazy. ("No thread context and no beer make Ruby go 
something something...").

Nick

Daniel Berger wrote:
> Hi all,
> 
> I've released the highly experimental first version of win32-thread.
> This code is ultra-alpha, and has already been banned in 37 countries.
> Oh, but not yours.
> 
> What is it?
> ===========
> A probably-naive attempt to wrap native Win32 threads for Ruby.
> 
> Where is it?
> ============
> You can find in on the RAA or on the Win32Utils project page at
> http://www.rubyforge.org/projects/win32utils.
> 
> What's wrong with it?
> =====================
> It only works for simple cases.  Attempting to create more than one
> native thread causes application errors and/or segfaults.  Not too
> useful at the moment, but barrels of fun.  Good at parties.
> 
> So why did you put it out?
> ==========================
> For kicks mainly, and for brave folks to tinker with.  I'm also hoping
> someone out there smarter than me might take a look and find a way to
> make it better. :)
> 
> Enjoy!
> 
> - Dan
> 
> 
> 
> 
>