From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org,
Alejandro Colomar <colomar.6.4.3@gmail.com>
Subject: [PATCH 1/2] system_data_types.7: Add va_list
Date: Sat, 26 Sep 2020 19:08:14 +0200 [thread overview]
Message-ID: <20200926170814.2121307-1-colomar.6.4.3@gmail.com> (raw)
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
man7/system_data_types.7 | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
index ae8fb6493..361e8d411 100644
--- a/man7/system_data_types.7
+++ b/man7/system_data_types.7
@@ -1116,6 +1116,37 @@ See also:
.BR getpwnam (2),
.BR credentials (7)
.RE
+.\"------------------------------------- va_list ----------------------/
+.TP
+.I va_list
+.RS
+.PP
+Include:
+.IR <stdarg> ;
+or
+.I <stdio.h>
+or
+.IR <wchar.h> .
+.PP
+Used by functions with a varying number of arguments of varying types.
+The function must declare an object of type
+.I va_list
+which is used by the macros
+.BR va_start (3),
+.BR va_arg (3),
+.BR va_copy (3)
+and
+.BR va_end (3)
+to traverse the list of arguments.
+.PP
+Conforming to: C99 and later; POSIX.1-2001 and later.
+.PP
+See also:
+.BR va_start (3),
+.BR va_arg (3),
+.BR va_copy (3),
+.BR va_end (3)
+.RE
.\"--------------------------------------------------------------------/
.SH NOTES
The structures described in this manual page shall contain,
--
2.28.0
next reply other threads:[~2020-09-26 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 17:08 Alejandro Colomar [this message]
2020-09-26 17:08 ` [PATCH 2/2] va_list.3: New link to system_data_types(7) Alejandro Colomar
2020-09-26 20:13 ` Michael Kerrisk (man-pages)
2020-09-26 20:13 ` [PATCH 1/2] system_data_types.7: Add va_list Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200926170814.2121307-1-colomar.6.4.3@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).