-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Andreas Büning on 6/22/2006 1:29 PM:
However, I thought that this behaviour of system() was common on DOS/Win*/OS/2
systems.
system(xcopy non_existing_file) returns 1 for example.
That's not a problem, unless:
FILE*f;
int result;
Eric Blake asked:
Is it worth adding a system module to gnulib that detects implementations
with
this bug, and provides rpl_system to work around it?
The specification of system() in ISO C 99 does not specify
1) which is the command processor,
and in particular which are the built
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/22/2006 5:37 AM:
Eric Blake wrote:
Is it worth adding a system module to gnulib that detects implementations
with
this bug, and provides rpl_system to work around it?
How many programs will be ported to OS/2
Eric Blake wrote:
According to Bruno Haible on 6/22/2006 5:37 AM:
Eric Blake wrote:
Is it worth adding a system module to gnulib that detects implementations
with
this bug, and provides rpl_system to work around it?
How many programs will be ported to OS/2? How active is the EMX-OS/2
() and pclose() use (status8)0xff, but system()
uses status0xff, to represent the low 8 bits returned from main() in the child
process.
Is it worth adding a system module to gnulib that detects implementations with
this bug, and provides rpl_system to work around it?
--
Eric Blake
