Re: EMX runtime and command line arguments
Ilya Zakharevich <nospam-abuse-qlYHBhoNh+/[email protected]> Sat, 17 Jan 2004 17:14:53 -0800
| Newsgroups | gmane.comp.ide.emx.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Jan 17, 2004 at 09:36:40PM +0100, Andreas Buening wrote: > Just to make sure I've understood correctly: If I want to run > a cmd command line with spawn*() then I can use > argv[0] = "cmd"; > argv[1] = "/c"; > argv[2] = "very long command line"; > argv[3] = NULL; > > which is 100% identical to the case if I split the command > line into pieces like the following: > > argv[0] = "cmd"; > argv[1] = "/c"; > argv[2] = "very"; > argv[3] = "long"; > argv[4] = "command"; > argv[5] = "line"; > argv[6] = NULL; > Is this correct? executables spawn()ed with different argc/argv will get *different* command lines. However, it may happen that in the case of cmd.exe the *interpretation* which cmd.exe gives to these two different command lines is going to be the same. Hard to tell, since the syntax used by cmd.exe is not documented! > Are there any known limits for the cmd command line arguments? 32K for the command line, and 32K for environment. Hope this helps, Ilya