From: Rich Kilmer <rich@...>
Date: 2002-11-06T05:48:53+09:00
Subject: Re: Win32 support issues

I don't think its 'fork' the command, but fork-like behavior.  Its weird
that on win32 you can use win32ole to start and drive any COM/OLE
component (word, IE, excel) but you cannot start another command-line
executable and drive its behavior (through stdin/out/err).  This would
be enabled by open3/popen3 (which under unix is implemented via fork.

-rich

> -----Original Message-----
> From: Lyle Johnson [mailto:lyle@users.sourceforge.net] 
> Sent: Tuesday, November 05, 2002 12:23 PM
> To: ruby-talk ML
> Subject: Re: Win32 support issues
> 
> 
> Gavin Sinclair wrote:
> 
> > What does this mean?  What Win32 support issues, apart from fork(), 
> > are there?
> 
> I would only answer that, if you don't get any specific answers there 
> probably are no Win32 support issues ;)
> 
> It has always been a little curious to me that people 
> consider the lack 
> of fork() -- a Unix-specific system call -- to be a "bug" in 
> the Win32 
> version of Ruby. I wonder if those people consider the fact 
> that Ruby's 
> Win32API module doesn't work under Linux a bug?
> 
> 
> 
>