[#3986] Re: Principle of least effort -- another Ruby virtue. — Andrew Hunt <andy@...>

> Principle of Least Effort.

14 messages 2000/07/14

[#4043] What are you using Ruby for? — Dave Thomas <Dave@...>

16 messages 2000/07/16

[#4139] Facilitating Ruby self-propagation with the rig-it autopolymorph application. — Conrad Schneiker <schneik@...>

Hi,

11 messages 2000/07/20

[ruby-talk:03870] Re: Multithreaded/Embedded Ruby?

From: "Warren Postma" <embed@...>
Date: 2000-07-06 13:17:52 UTC
List: ruby-talk #3870
"Yukihiro Matsumoto" <matz@netlab.co.jp> wrote in message
news:E137vWV-0002iY-00@ev...
> Hi,
>
> In message "[ruby-talk:03708] Re: Multithreaded/Embedded Ruby?"
>     on 00/06/30, "R. Hotaka" <hotaka@media.teu.ac.jp> writes:
>
> |If a thread can read (but not write) the value of a variable defined in
(or possesed by)
> |another thread, can we say that situation "thread safe"?
>
> I guess something is thread safe, if and only if it's safe in ANY
condition.
> So, if the situation is designed to be so, it's thread safe, otherwise
> it's happen to be safe in that particular occasion.
>
> matz.


So in this case, nobody has answered my question: Is the Ruby interpreter
thread safe (which would indeed be a marvel), or are there some
interlocks/mutexes in there to make it thread safe, or is that an experiment
not yet attempted?

Warren Postma




In This Thread