erik quanstrom wrote: > > That's why many OSes have a "spawn" primitive that combines fork-and-exec. > the problem with spawn is it requires a mechanism to replace that little > block of code between the fork and exec. that code is hardly ever the > same so spawn keeps growing arguments.
Yes, on the other hand I bet a spawn interface could be devised that is sufficiently programmable. (May require some extra dup()s etc. to really handle all the common usage patterns.)
