[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Embedding ruby 1.9 using native threads

Deb 123

2/7/2008 5:46:00 PM

Hi All,
I've heard that the new ruby interpreter v1.9 is able to handle native
OS threads. However, i've tried a few different ways of running
multiple interpreters in separate threads (on XP), and it doesn't seem
to work. Is there any special initialization to make to the ruby
interpreter, or something i might be missing?

Thanks!
--
Posted via http://www.ruby-....
2 Answers

Tom M

2/7/2008 6:52:00 PM

0


On Feb 7, 12:45 pm, Deb 123 <deba...@sympatico.ca> wrote:
> Hi All,
> I've heard that the new ruby interpreter v1.9 is able to handle native
> OS threads. However, i've tried a few different ways of running
> multiple interpreters in separate threads (on XP), and it doesn't seem
> to work. Is there any special initialization to make to the ruby
> interpreter, or something i might be missing?
>
> Thanks!
> --
> Posted viahttp://www.ruby-....

I am not sure, but just as a warning, I don't think 1.9 native threads
don't deliver what you might think. It's my understanding that while
there is native thread support, there will be a global interpreter
lock, so that for virtually everything happening only one thread will
be executing at a time pretty much all the time.

Deb 123

2/20/2008 10:16:00 PM

0

Tom M wrote:
> On Feb 7, 12:45 pm, Deb 123 <deba...@sympatico.ca> wrote:
>> Hi All,
>> I've heard that the new ruby interpreter v1.9 is able to handle native
>> OS threads. However, i've tried a few different ways of running
>> multiple interpreters in separate threads (on XP), and it doesn't seem
>> to work. Is there any special initialization to make to the ruby
>> interpreter, or something i might be missing?
>>
>> Thanks!
>> --
>> Posted viahttp://www.ruby-....
>
> I am not sure, but just as a warning, I don't think 1.9 native threads
> don't deliver what you might think. It's my understanding that while
> there is native thread support, there will be a global interpreter
> lock, so that for virtually everything happening only one thread will
> be executing at a time pretty much all the time.

Thanks Tom, Sorry for the late reply. So it's multithreading, but it
still has to run sequentially.. Well I guess i'll have to find a way
around it ;)
Thanks for clearing that up!
--
Posted via http://www.ruby-....