Stdarg.h

  is a header in the C standard library of the C programming language that allows functions to accept an indefinite number of arguments. It provides facilities for stepping through a list of function arguments of unknown number and type. C++ provides this functionality in the header.

The contents of  are typically used in variadic functions, though they may be used in other functions (for example,  ) called by variadic functions.

Declaring variadic functions
Variadic functions are functions which may take a variable number of arguments and are declared with an ellipsis in place of the last parameter. An example of such a function is. A typical declaration is

Variadic functions must have at least one named parameter, so, for instance,

is not allowed in C17 and earlier. (In C++ and C23, such a declaration is permitted.) In C, a comma must precede the ellipsis if a named parameter is specified; in C++, it is optional.

Defining variadic functions
The same syntax is used in a definition:

An ellipsis may not appear in old-style function definitions.

Accessing the arguments
To access the unnamed arguments, one must declare a variable of type  in the variadic function. The macro  is then called with two arguments: the first is the variable declared of the type , the second is the name of the last named parameter of the function. In C23 the second argument will be optional and will not be evaluated. After this, each invocation of the  macro yields the next argument. The first argument to  is the   and the second is the type of the next argument passed to the function. Finally, the  macro must be called on the   before the function returns. (It is not required to read in all the arguments.)

C99 provides an additional macro,, which can duplicate the state of a. The macro invocation  copies   into.

There is no defined method for counting or classifying the unnamed arguments passed to the function. The function is simply required to know or determine this somehow, the means of which vary. Common conventions include:
 * Use of a  or  -like format string with embedded specifiers that indicate argument types.
 * A sentinel value at the end of the variadic arguments.
 * A count argument indicating the number of variadic arguments.

Passing unnamed arguments to other calls
Because the size of the unnamed argument list is generally unknown (the calling conventions employed by most compilers do not permit determining the size of the unnamed argument block pointed at by  inside the receiving function), there is also no reliable, generic way to forward the unnamed arguments into another variadic function. Even where determining the size of the argument list is possible by indirect means (for example, by parsing the format string of ), there is no portable way to pass the dynamically determined number of arguments into the inner variadic call, as the number and size of arguments passed into such calls must generally be known at compile time. To some extent, this restriction can be relaxed by employing variadic macros instead of variadic functions. Additionally, most standard library procedures provide -prefixed alternative versions which accept a reference to the unnamed argument list (i.e. an initialized   variable) instead of the unnamed argument list itself. For example,  is an alternate version of   expecting a   instead of the actual unnamed argument list. A user-defined variadic function can therefore initialize a  variable using   and pass it to an appropriate standard library function, in effect passing the unnamed argument list by reference instead of doing it by value. Because there is no reliable way to pass unnamed argument lists by value in C, providing variadic API functions without also providing equivalent functions accepting  instead is considered a bad programming practice.

Type safety
Some C implementations provide C extensions that allow the compiler to check for the proper use of format strings and sentinels. Barring these extensions, the compiler usually cannot check whether the unnamed arguments passed are of the type the function expects, or convert them to the required type. Therefore, care should be taken to ensure correctness in this regard, since undefined behavior results if the types do not match. For example, if the expected type is, then a null pointer should be passed as. Writing just  would result in an argument of type either   or , neither of which is correct. Another consideration is the default argument promotions applied to the unnamed arguments. A  will automatically be promoted to a. Likewise, arguments of types narrower than an  will be promoted to   or. The function receiving the unnamed arguments must expect the promoted type.

GCC has an extension that checks the passed arguments:

"

The format attribute specifies that a function takes,,   or   style arguments which should be type-checked against a format string. For example, the declaration:

causes the compiler to check the arguments in calls to  for consistency with the   style format string argument."

Example
This program yields the output:

5 2 14 84 97 15 84 51

1

To call other var args functions from within your function (such as sprintf) you need to use the var arg version of the function (vsprintf in this example):

varargs.h
Outdated versions of POSIX defined the legacy header, which dates from before the standardization of C and provides functionality similar to. This header is part of neither ISO C nor POSIX. The file, as defined in the second version of the Single UNIX Specification, simply contains all of the functionality of C89, with the exceptions that:
 * it cannot be used in standard C new-style definitions
 * the given argument may be omitted (standard C requires at least one argument)

The interface is also different. For printargs example, one would instead write:

and is called the same way.

requires old-style function definitions because of the way the implementation works. Conversely, it is not possible to mix old-style function definitions with.