[#4479] Requesting addition to IRB (configurable standard output) — Sascha Ebach <se@...>

Hello,

13 messages 2005/02/24
[#4482] Re: Requesting addition to IRB (configurable standard output) — Sam Roberts <sroberts@...> 2005/02/25

Quoting se@digitale-wertschoepfung.de, on Fri, Feb 25, 2005 at 01:22:34AM +0900:

[#4483] Re: Requesting addition to IRB (configurable standard output) — Eric Hodel <drbrain@...7.net> 2005/02/25

On 24 Feb 2005, at 19:51, Sam Roberts wrote:

[#4488] Re: Requesting addition to IRB (configurable standard output) — Sam Roberts <sroberts@...> 2005/02/26

Quoting drbrain@segment7.net, on Sat, Feb 26, 2005 at 02:43:31AM +0900:

[#4489] Re: Requesting addition to IRB (configurable standard output) — Eric Hodel <drbrain@...7.net> 2005/02/26

On 25 Feb 2005, at 16:03, Sam Roberts wrote:

Re: Thread-safe Ruby Status?

From: Vincent Isambart <vincent.isambart@...>
Date: 2005-02-16 14:44:44 UTC
List: ruby-core #4442
Hi,

> |I saw in the ChangeLog in the CVS trunk some recent modifications
> |regarding the threads and discovered the _THREAD_SAFE flag in eval.c.
> |So I was wondering what is the current status of the thread-safeness
> |of the Ruby interpreter in the CVS trunk. And has some work on Ruby
> |using native threads instead of its owns begun?
> 
> _THREAD_SAFE means to avoid crashing when pthread enabled library is
> linked, not replacing Ruby thread with pthread.
And regarding the thread-safeness of the interpreter itself - by that
I mean being able to run more than one Ruby interpreter in one
process, what is the current status? I remember at least a big part of
the variables that were global are not anymore, but I do not know what
is the current state of all this...

Thanks for the fast replies :)

oyasumi nasai (it's quite late in Japan ;))
Kind regards,
Vincent "scritch" Isambart

In This Thread