From: Simon Strandgaard <0bz63fz3m1qt3001@...>
Date: 2003-05-12T20:00:56+09:00
Subject: Re: RCR for child execution

On Mon, 12 May 2003 18:32:47 +0900, Yukihiro Matsumoto wrote:
>
> I'm not sure if I understand what you care, but at least I want you to
> know it's the field I want to fix/change before the final 1.8.0
> release.

I think the best description of the problem I have come up with so far is:
http://ruby-talk.com/cgi-bin/scat.rb/ruby/ruby-talk/71191


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 ???


Thanks for Ruby :-)

--
Simon Strandgaard