Comment author: administrator

usage:
Unix.create_process program.exe [| p1; p2; ...; pn |] ...

Symptom 1: p1 is not the first paramater for program.exe. It simply
vanishes.

This is normal Unix and Windows behavior: the first element of the
argument array is "parameter number zero" (argv[0] in C). Most of the
time, you want to put the program name ("program.exe" in your example)
as this parameter 0, but in rare cases a different value for that
parameter can be useful.

Symptom 2: if the path to program.exe contains spaces, the first parameter
is the second part of this path. p1 is ignored as before.

I haven't been able to reproduce this behavior, using an MSVC-compiled
executable as program.exe. It is true that if the parameters p0 ... pN
contain spaces and are not quoted, program.exe will split the
parameters at spaces, causing a mismatch. It might be argued that
create_process should do the quoting itself. But this looks like a
different issue than what you observe. Can you provide an example?

• Xavier Leroy

Comment author: administrator

Added quoting of arguments 2004-06-12, XL. Symtpom 2 cannot be reproduced with
a C program as target; seems to occur only for batch files; looks like a "cmd"
shell problem, not ours.