This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Fix documented parameters to execle
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: libc-alpha at sourceware dot org
- Date: Fri, 17 Feb 2012 22:08:15 +0000 (UTC)
- Subject: Fix documented parameters to execle
Bug 10210 reports that the documentation of execle wrongly puts the
environment argument before rather than after the variable arguments for
program parameters; I've applied this patch to fix this. (Formally of
course a prototype with something after the "..." cannot be specified in
C, but putting the ... in the middle is the conventional way to express
what the arguments are to execle.)
2012-02-17 Joseph Myers <joseph@codesourcery.com>
[BZ #10210]
* manual/process.texi (execle): Move @dots{} before last argument.
diff --git a/manual/process.texi b/manual/process.texi
index 1946793..53d467c 100644
--- a/manual/process.texi
+++ b/manual/process.texi
@@ -321,7 +321,7 @@ variable; see @ref{Environment Access}.
@comment unistd.h
@comment POSIX.1
-@deftypefun int execle (const char *@var{filename}, const char *@var{arg0}, char *const @var{env}@t{[]}, @dots{})
+@deftypefun int execle (const char *@var{filename}, const char *@var{arg0}, @dots{}, char *const @var{env}@t{[]})
This is similar to @code{execl}, but permits you to specify the
environment for the new program explicitly. The environment argument is
passed following the null pointer that marks the last @var{argv}
--
Joseph S. Myers
joseph@codesourcery.com