From: "Iñaki Baz Castillo" <ibc@...>
Date: 2012-05-16T16:33:06+09:00
Subject: Re: How to ensure that a block runs entirely after other threads? (Thread.exclusive does not "work")

2012/5/16 Robert Klemme <shortcutter@googlemail.com>:
> I do not know your sharing and exclusiveness requirements but one
> helpful option might be a read write lock.  Or, of course, a regular
> mutex.  In any case you need to define in code which threads share
> which resources and hence require exclusive access.

Hi, thanks to both.

First of all, as Eric said, Thread.exclusive does "nothing" in Ruby
1.9 (native threads), so I need to use something like Mutex, but that
requires cooperation  from all the threads which could not be my case
(I'm coding a Ruby library rather than a final application).

But it's ok, I'll document that, in case the user wants to use
multiple threads, it is his responsability to syncronize them.

Thanks a lot.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>