Re: Future [exec] overhaul

Larry McVoy wrote:
> We've been pretty happy with ours even though it doesn't fork /bin/sh.
> And the nice thing is it works when there is no /bin/sh (winblows).

Firing off /bin/sh as a subprocess is no big deal. When I'm in a
situation where I'm exposing some scripting capability to users without
giving them full Tcl (or Perl, or whatever) I'll often use /bin/sh since
then they can use a syntax that they're used to. As a plus, the overhead
is pretty small; shell scripts start up processes all the time and
nobody's too worried about that. I'd do the same on Windows, except
there users tend to know one end of a shell from the other...

Donal.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08