From: Simon Strandgaard <0bz63fz3m1qt3001@...>
Date: 2003-05-13T00:23:17+09:00
Subject: Re: RCR for child execution

On Mon, 12 May 2003 21:12:15 +0900, Hal E. Fulton wrote:

> From: "Simon Strandgaard" <0bz63fz3m1qt3001@sneakemail.com>
>> Separation of ruby stdout/stderr from C/C++ stdout/stderr is what I want.
>> I run Ruby in the same thread as C++ (ruby embedded into C++).
>> This separation is working fine, as long as I don't use system or
>> backquote.
>>
>> Using system or backquote, then it goes BOOM. The problem as I see it is
>> localized in Rubys code - not mine!  Ruby spawns a child which inherits
>> stdout/stderr.  This child should instead inherit rb_stdout/rb_stderr
>> instead!!!    Can this issue be fixed on Ruby ???
> 
> If I understand you correctly, I think it is
> an operating system issue rather than a Ruby
> issue.

Im trying to make it easier to embed ruby into existing C/C++
applications. I think this issue is very important in order to get Ruby more
widespread.
 

--
Simon Strandgaard