David Boyce wrote:
> At 11:30 AM 1/31/01 -0500, John Porter wrote:
>
> >Huh? exec() works! At least on some versions of Windows.
>
> It "works" in the sense that it passes the arguments to the exec() in the
> Windows CRTL. Unfortunately the underlying Windows exec has
> non-traditional, to put it politely, semantics. It behaves sort of like a
> fork/exec sequence without the wait; i.e. it starts a new process in the
> background and returns control immediately to the calling process.
Well, maybe system() does that, but exec() does not return at all.
If you're using exec, why do you care?
> In any case, the plain fact is that 'system @cmd'
> and 'system "@cmd"' are indistinguishable on Windows despite what the doc
> so plainly says.
Why do you care?
--
John Porter
