On Mon, Feb 15, 2010 at 11:17 AM, Jimmy Schementi <
jimmy.scheme...@microsoft.com> wrote:
> IronRuby maps Ruby’s green threads directly to CLR threads, and there is no
> GIL.
>
Holy race conditions, batman! I'll be a lot more careful calling Thread.new
now :-)
..@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Orion Edwards
Sent: Sunday, February 14, 2010 1:19 PM
To: ironruby-core@rubyforge.org
Subject: [Ironruby-core] Threading model
Here is what I *think* happens:
- Thread.new and the other ruby threading methods from the ruby standa
Here is what I *think* happens:
- Thread.new and the other ruby threading methods from the ruby standard
library will create and run on new CLR threads, but there is 'global
interpreter lock' type thing to emulate MRI
- I can sidestep the GIL by explicitly using underlying CLR threading
methods
