Mail Archives: djgpp/1994/04/07/15:31:56
> How are extended command lines handled? (the typical way on dos is to
> pass them via the environment). The caller puts the command line
> in the environment, and the callee pulls it out when it builds argc/argv...
go32 (and V2.0) accept the following conventions:
* dos's 128-byte command line
* environment variables _argc, _argvN (the GNUish method)
* !proxy pointers (stub's method)
* @file response file (Borland, some Microsoft)
go32 also expands unquoted wildcards. When libc's spawn() calls a
program, it uses the !proxy method when calling another djgpp app
(which is why make knows about gcc) and the 128-byte command line
otherwise.
- Raw text -