S
Steve [RubyTalk]
I understand from the documentation that when I embed Ruby in a native
application that the Ruby interpreter is not thread safe - i.e. that I
can't concurrently evaluate different ruby expressions in separate
native threads - if my application is multi-threaded that I must somehow
enforce mutual exclusion myself. This seems pretty restrictive -
especially with today's multi-processor servers and hyper-threading.
Are there any plans to make a future version of Ruby thread safe? Can
anyone comment as to how difficult it would likely prove to modify Ruby
1.8 to establish a bespoke version which is thread safe? Is there a
good reason for the decision to use global variables in the
implementation of the ruby interpreter which would make such
modifications undesirable to the wider Ruby community?
application that the Ruby interpreter is not thread safe - i.e. that I
can't concurrently evaluate different ruby expressions in separate
native threads - if my application is multi-threaded that I must somehow
enforce mutual exclusion myself. This seems pretty restrictive -
especially with today's multi-processor servers and hyper-threading.
Are there any plans to make a future version of Ruby thread safe? Can
anyone comment as to how difficult it would likely prove to modify Ruby
1.8 to establish a bespoke version which is thread safe? Is there a
good reason for the decision to use global variables in the
implementation of the ruby interpreter which would make such
modifications undesirable to the wider Ruby community?