From: Rich Kilmer <rich@...>
Date: 2002-11-06T06:57:31+09:00
Subject: Re: Win32 support issues

That is my understanding as well and it is this copying of the process
image that win32 does not have (as far as I know).  This should not
preclude starting another process and aquiring pipes to the
stdin/out/err, which would serve the FreeRIDE project's needs (and
likely many others).  This is what I think popen3 should do under win32.

-rich

> -----Original Message-----
> From: Lyle Johnson [mailto:lyle@users.sourceforge.net] 
> Sent: Tuesday, November 05, 2002 4:44 PM
> To: ruby-talk ML
> Subject: Re: Win32 support issues
> 
> 
> Rich Kilmer wrote:
> 
> > 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).
> 
> My understanding was that the main difference between fork() and the 
> Win32 function CreateProcess() is that fork() makes a copy of 
> the entire 
> process image, whereas CreateProcess() does not. Are there some other 
> significant differences that you're seeing?
> 
> 
> 
>