On Sun, Jul 27, 2014 at 6:38 AM, Philip Guenther <guent...@gmail.com> wrote: > ... > > That phrasing seems wrong: the environment pointer in execvpe() doesn't > follow "the null pointer that terminates the list of arguments". Something > more is needed to cover both.
The sentence continued, "or the pointer to the argv array", which refers to execvpe(). How about something more succinct? The patch below removes the mention of the parameters of execle() and execvpe() in the fifth paragraph since both parameters are described in detail in the third and fourth paragraphs, respectively. Index: exec.3 =================================================================== RCS file: /cvs/src/lib/libc/gen/exec.3,v retrieving revision 1.25 diff -u -p -r1.25 exec.3 --- exec.3 21 Jan 2014 03:15:45 -0000 1.25 +++ exec.3 31 Jul 2014 01:46:29 -0000 @@ -103,12 +103,10 @@ be terminated by a null pointer itself. .Pp The .Fn execle -function also specifies the environment of the executed process by following -the null -pointer that terminates the list of arguments in the parameter list -or the pointer to the -.Va argv -array with an additional parameter. +and +.Fn execvpe +functions also specify the environment of the executed process +with an additional parameter. This additional parameter is an array of pointers to NUL-terminated strings and .Em must
