aboutsummaryrefslogtreecommitdiffstats
path: root/man3/stdarg.3
diff options
context:
space:
mode:
Diffstat (limited to 'man3/stdarg.3')
-rw-r--r--man3/stdarg.310
1 files changed, 5 insertions, 5 deletions
diff --git a/man3/stdarg.3 b/man3/stdarg.3
index 4cec3d3c49..16ee5b5186 100644
--- a/man3/stdarg.3
+++ b/man3/stdarg.3
@@ -57,12 +57,12 @@ types.
The include file
.I <stdarg.h>
declares a type
-.B va_list
+.I va_list
and defines three macros for stepping through a list of arguments whose
number and types are not known to the called function.
.PP
The called function must declare an object of type
-.B va_list
+.I va_list
which is used by the macros
.BR va_start (),
.BR va_arg (),
@@ -96,7 +96,7 @@ argument in the call.
The parameter
.I ap
is the
-.B va_list
+.I va_list
.I ap
initialized by
.BR va_start ().
@@ -153,7 +153,7 @@ may be a macro or a function.
.SS va_copy()
.\" Proposal from clive@demon.net, 1997-02-28
An obvious implementation would have a
-.B va_list
+.I va_list
be a pointer to the stack frame of the variadic function.
In such a setup (by far the most common) there seems
nothing against an assignment
@@ -266,7 +266,7 @@ code to
.B stdarg
code, but it also creates difficulties for variadic functions that wish to
pass all of their arguments on to a function that takes a
-.B va_list
+.I va_list
argument, such as
.BR vfprintf (3).
.SH EXAMPLE