From: "Hal E. Fulton" <hal9000@...>
Date: 2003-05-12T20:12:15+09:00
Subject: Re: RCR for child execution

----- Original Message -----
From: "Simon Strandgaard" <0bz63fz3m1qt3001@sneakemail.com>
Newsgroups: comp.lang.ruby
To: "ruby-talk ML" <ruby-talk@ruby-lang.org>
Sent: Monday, May 12, 2003 6:00 AM
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 ???

If I understand you correctly, I think it is
an operating system issue rather than a Ruby
issue.

I sympathize with what you're trying to do,
but I don't know how to make it work.

Hal