Dennis Newbold wrote:

>     H'mm .. a pseudo child process which lives in the same address space
>     as its parent.  Sounds pretty much like a thread to me.  Ruby already
>     has threads.  So.. as a bottom line .. if under Windows, we alias
>     fork to Thread.new, we can add to Ruby the same level of fork()
>     that ActiveState just spent umpteen thousand man-hours putting in.

Ruby threads are within the process, not OS threads. So if the reason
you're forking is to call system(), then you can't get fork behavior
from threads.