note BrowserUk <blockquote><i></i></blockquote> <p>For a very large proportion of uses of [fork] -- essentially all those using the 'fork & exec' idiom -- [system], especially <c>system 1, ...</c> is a far more effective 'emulation'. The spawned process can (by default does) inherit many of the system resources -- open file, pipe and socket handles and the like -- that forked processes inherit under *nix. <p>But, as [Corion] correctly points out, there are limitations that prevent it from being a transparent solution to porting [fork]ing programs to Windows. <p>It is possible to provide a more realistic and efficient [fork] emulation on Windows -- one that uses real processes and even COW memory. Creating the new process and giving it COW access to the parents memory segments is relatively trivial. The difficult part is fixing up the perl internals within the spawned copy. <div class="pmsig"><div class="pmsig-171588"> <hr /> <font size=1 > <div>Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.</div> <div>"Science is about questioning the status quo. Questioning authority". </div> <div>In the absence of evidence, opinion is indistinguishable from prejudice.</div> </font> </div></div> 929097 930816