I believe that is exactly what happens underneath, anyway, and indeed,
the results are the same. It seems that cmd.exe is paying special
attention to scripts writing to stdout, and if a failure occurs it
writes the failure message to stderr.
DJ
Greg Thomas wrote:
> On Thu, 14 Aug 2003 18:18:01 -0600, "D.J. Heap" <dj@shadyvale.net>
> wrote:
>
>
>>Very weird, since it doesn't seem to apply to exe's (probably, cmd.exe
>>is 'helping' by printing error messages to stderr or something and
>>normal exe's just ignore the write failure).
>
>
> Could you run the .bat/.cmd as a .exe, making them the same, by
> calling the command interpreter (which is a .exe) with the /C flag -
> i.e. something like
>
> BOOL rc = CreateProcess( "%COMSPEC% /C c:\\temp\\test.cmd" );
>
> Greg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 16 16:51:51 2003