Bug 3158 – (D1 only) std.process.execv() incorrect documentation

Phobos in DMD 2.031, 2.030, 1.045 on Windows XP SP3: function int std.process.execv(in string pathname, in immutable(char)[][] argv) not return any value, but terminate application. Short example - caller.exe should run called.exe, then print returned value: /*** begin file caller.d */ import std.process; import std.stdio; void main() { string[] args = ["a1", "b2", "c3"]; int res = std.process.execv("called.exe", args); writefln("res=%d", res); /*this line never executed*/ }/*** end file caller.d */ In Windiws XP environment caller.exe terminates with code 0 while executing execv() function, and writefln() never executed - no any output occure; Under debug we can see calls: _Dmain -> std@process@execv -> _execv -> ___spawn -> sub_4263F0 -> _exec -> _exit

This is spec is almost certainly wrong because the POSIX exec* calls replace the current process with whatever it is called with, The function never returns unless something goes wrong. These functions should be renamed or re speced.

exec* calls bahaves this way. So IMHO documentation should be fixed.

Sorry, accidentally closed, reopening.

This is documented in the current version. All bugs on Phobos and DMD related to D1 were closed, so I think it's prudent to do so here as well. D does not have the man power to fix doc issues in older versions.