From: Benoit Cerrina Date: 2002-03-20T16:42:00+09:00 Subject: Re: Development of Windows version of Ruby here is the output from the forker sample in the activestate perl distrib (I changed it to fork 5 times instead of 32 for legibility E:\perl\eg\fork>perl forker.pl Entering SharedInit() 13060 spawned -1540 13060 spawned -1556 13060 spawned -1520 13060 spawned -648 -1540 child of 13060 -1540 Entering Work() -1540 exiting -1556 child of 13060 -1556 Entering Work() -1556 exiting -1520 child of 13060 -1520 Entering Work() -1520 exiting -648 child of 13060 -648 Entering Work() -648 exiting 13060 spawned -1528 13060 to reap -1540 13060 to reap -1556 13060 to reap -1520 1-1528 child of 13060 -1528 Entering Work() -1528 exiting 3060 to reap -648 13060 to reap -1528 13060 exiting E:\perl\eg\fork> this is on win32. You are right it can be done "Jason Voegele" wrote in message news:3856.198.133.202.18.1016551313.squirrel@12.27.88.122... > > I am both delighted and saddened at this thread; Delighted that > > windows users are coming face to face with some of the > > deficiences of the windows os and saddened that they are > > attempting to scapegoat Ruby for window's failings. > > But if certain P languages support those features it makes it look as if it > is Ruby's failing. I think that's the issue people are referring to. > > > I personally could care less if Ruby ever gets popular on > > windows. After all, you have VB, right? > > Some of us *have* to use Windows--corporate "standards" and other such > nonsense--but choose to use Ruby. I like Ruby, and wouldn't touch VB with > a 10 foot Python. > > Jason Voegele > >