Variadic function

<h2 id="overview">Overview</h2>
<p>There are many mathematical and logical operations that come across naturally as variadic functions. For instance, the summing of numbers or the <a href="/facts/Concatenation/1npYg6rc">concatenation</a> of strings or other sequences are operations that can be thought of as applicable to any number of operands (even though formally in these cases the <a href="/facts/Associative_property/EQX8lV6r">associative property</a> is applied).
</p><p>Another operation that has been implemented as a variadic function in many languages is output formatting. The <a href="/facts/C_(programming_language)/Ky2No763">C</a> function <a href="/facts/Printf/Sc6Czbp2">printf</a> and the <a href="/facts/Common_Lisp/mq1pRbSF">Common Lisp</a> function <a href="/facts/Format_(Common_Lisp)/VKSeEbhC">format</a> are two such examples. Both take one argument that specifies the formatting of the output, and <i>any number</i> of arguments that provide the values to be formatted.
</p><p>Variadic functions can expose <a href="/facts/Type_safety/WxmEKq8R">type-safety</a> problems in some languages. For instance, C's printf, if used incautiously, can give rise to a class of security holes known as <a href="/facts/Format_string_attack/hBvaxceE">format string attacks</a>. The attack is possible because the language support for variadic functions is not type-safe: it permits the function to attempt to pop more arguments off the <a href="/facts/Stack_(abstract_data_type)/bj7l94v1">stack</a> than were placed there, corrupting the stack and leading to unexpected behavior. As a consequence of this, the <a href="/facts/CERT_Coordination_Center/9JD4Y8uQ">CERT Coordination Center</a> considers variadic functions in C to be a high-severity security risk.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a>
</p><p>In <a href="/facts/Functional_programming/cdxqPEIM">functional programming</a> languages, variadics can be considered complementary to the <a href="/facts/Apply/2Emq4vwk">apply</a> function, which takes a function and a list/sequence/array as arguments, and calls the function with the arguments supplied in that list, thus passing a variable number of arguments to the function. In the functional language <a href="/facts/Haskell/ydEsHuGy">Haskell</a>, variadic functions can be implemented by returning a value of a <a href="/facts/Type_class/MBbIhF4n">type class</a> T; if instances of T are a final return value r and a function (T t) => x -> t, this allows for any number of additional arguments x.
</p><p>A related subject in <a href="/facts/Term_rewriting/9PHlnnnJ">term rewriting</a> research is called hedges, or hedge variables.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> Unlike variadics, which are functions with arguments, hedges are sequences of arguments themselves. They also can have constraints ('take no more than 4 arguments', for example) to the point where they are not variable-length (such as 'take exactly 4 arguments') - thus calling them <i>variadics</i> can be misleading. However they are referring to the same phenomenon, and sometimes the phrasing is mixed, resulting in names such as <i>variadic variable</i> (synonymous to hedge). Note the double meaning of the word <i>variable</i> and the difference between arguments and variables in functional programming and term rewriting. For example, a term (function) can have three variables, one of them a hedge, thus allowing the term to take three or more arguments (or two or more if the hedge is allowed to be empty).
</p>
<h2 id="examples">Examples</h2>
<h3>In C</h3>
<p>To portably implement variadic functions in the <a href="/facts/C_(programming_language)/Ky2No763">C language</a>, the standard <a href="/facts/Stdarg.h/xhACIm7I">stdarg.h</a> header file is used. The older <a href="/facts/Varargs.h/xhACIm7I">varargs.h</a> header has been <a href="/facts/Deprecation/1aQL7rnP">deprecated</a> in favor of stdarg.h. In C++, the header file cstdarg is used.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a>
</p>
#include <stdarg.h>
#include <stdio.h>

double average(int count, ...) {
    va_list ap;
    int j;
    double sum = 0;

va_start(ap, count); /* Before C23: Requires the last fixed parameter (to get the address) */
    for (j = 0; j < count; j++) {
        sum += va_arg(ap, int); /* Increments ap to the next argument. */
    }
    va_end(ap);

return sum / count;
}

int main(int argc, char const *argv[]) {
    printf("%f\n", average(3, 1, 2, 3));
    return 0;
}

<p>This will compute the average of an arbitrary number of arguments. Note that the function does not know the number of arguments or their types. The above function expects that the types will be int, and that the number of arguments is passed in the first argument (this is a frequent usage but by no means enforced by the language or compiler). In some other cases, for example <a href="/facts/Printf/Sc6Czbp2">printf</a>, the number and types of arguments are figured out from a format string. In both cases, this depends on the programmer to supply the correct information. (Alternatively, a <a href="/facts/Sentinel_value/Ma1rxg1q">sentinel value</a> like NULL or nullptr may be used to indicate the end of the parameter list.) If fewer arguments are passed in than the function believes, or the types of arguments are incorrect, this could cause it to read into invalid areas of memory and can lead to vulnerabilities like the <a href="/facts/Format_string_attack/hBvaxceE">format string attack</a>. Depending on the system, even using NULL as a sentinel may encounter such problems; nullptr or a dedicated null pointer of the correct target type may be used to avoid them. 
</p><p>stdarg.h declares a type, va_list, and defines four macros: <a href="/facts/Va_start/xhACIm7I">va_start</a>, <a href="/facts/Va_arg/xhACIm7I">va_arg</a>, <a href="/facts/Va_copy/xhACIm7I">va_copy</a>, and <a href="/facts/Va_end/xhACIm7I">va_end</a>. Each invocation of va_start and va_copy must be matched by a corresponding invocation of va_end. When working with variable arguments, a function normally declares a variable of type va_list (ap in the example) that will be manipulated by the macros.
</p>
<ol><li>va_start takes two arguments, a va_list object and a reference to the function's last parameter (the one before the ellipsis; the macro uses this to get its bearings). In <a href="/facts/C23_(C_standard_revision)/1VvQNwSb">C23</a>, the second argument will no longer be required and variadic functions will no longer need a named parameter before the ellipsis.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a><a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> It initialises the va_list object for use by va_arg or va_copy. The compiler will normally issue a warning if the reference is incorrect (e.g. a reference to a different parameter than the last one, or a reference to a wholly different object), but will not prevent compilation from completing normally.</li>
<li>va_arg takes two arguments, a va_list object (previously initialised) and a type descriptor. It expands to the next variable argument, and has the specified type. Successive invocations of va_arg allow processing each of the variable arguments in turn. Unspecified behavior occurs if the type is incorrect or there is no next variable argument.</li>
<li>va_end takes one argument, a va_list object. It serves to clean up. If one wanted to, for instance, scan the variable arguments more than once, the programmer would re-initialise your va_list object by invoking va_end and then va_start again on it.</li>
<li>va_copy takes two arguments, both of them va_list objects. It clones the second (which must have been initialised) into the first. Going back to the "scan the variable arguments more than once" example, this could be achieved by invoking va_start on a first va_list, then using va_copy to clone it into a second va_list. After scanning the variable arguments a first time with va_arg and the first va_list (disposing of it with va_end), the programmer could scan the variable arguments a second time with va_arg and the second va_list. va_end needs to also be called on the cloned va_list before the containing function returns.</li></ol>
<h3>In C#</h3>
<p><a href="/facts/C_Sharp_(programming_language)/UC2gxeyb">C#</a> describes variadic functions using the params keyword. A type must be provided for the arguments, although object[] can be used as a catch-all. At the calling site, you can either list the arguments one by one, or hand over a pre-existing array having the required element type. Using the variadic form is <a href="/facts/Syntactic_sugar/FYkNSdTI">Syntactic sugar</a> for the latter.
</p>
using System;

class Program
{
    static int Foo(int a, int b, params int[] args)
    {
        // Return the sum of the integers in args, ignoring a and b.
        int sum = 0;
        foreach (int i in args)
            sum += i;
        return sum;
    }
        
    static void Main(string[] args)
    {
        Console.WriteLine(Foo(1, 2));  // 0
        Console.WriteLine(Foo(1, 2, 3, 10, 20));  // 33
        int[] manyValues = new int[] { 13, 14, 15 };
        Console.WriteLine(Foo(1, 2, manyValues));  // 42
    }
}

<h3>In C++</h3>
<p>The basic variadic facility in C++ is largely identical to that in C. The only difference is in the syntax, where the comma before the ellipsis can be omitted. C++ allows variadic functions without <a href="/facts/Named_parameter/GwoRa3B0">named parameters</a> but provides no way to access those arguments since va_start requires the name of the last fixed argument of the function. 
</p>
#include <iostream>
#include <cstdarg>

void simple_printf(const char* fmt...)      // C-style "const char* fmt, ..." is also valid
{
    va_list args;
    va_start(args, fmt);
 
    while (*fmt != '\0') {
        if (*fmt == 'd') {
            int i = va_arg(args, int);
            std::cout << i << '\n';
        } else if (*fmt == 'c') {
            // note automatic conversion to integral type
            int c = va_arg(args, int);
            std::cout << static_cast<char>(c) << '\n';
        } else if (*fmt == 'f') {
            double d = va_arg(args, double);
            std::cout << d << '\n';
        }
        ++fmt;
    }
 
    va_end(args);
}

int main()
{
    simple_printf("dcff", 3, 'a', 1.999, 42.5); 
}

<p><a href="/facts/Variadic_templates/LtR2h4b1">Variadic templates</a> (parameter pack) can also be used in C++ with language built-in <a href="/facts/Fold_(higher-order_function)/gllDcCxw">fold expressions</a>.
</p>
#include <iostream>

template <typename... Ts>
void foo_print(Ts... args) 
{
    ((std::cout << args << ' '), ...);
}

int main()
{
    std::cout << std::boolalpha;
    foo_print(1, 3.14f); // 1 3.14
    foo_print("Foo", 'b', true, nullptr); // Foo b true nullptr
}

<p>The <a href="/facts/CERT_Coding_Standards/qwgEwoUJ">CERT Coding Standards</a> for C++ strongly prefers the use of <a href="/facts/Variadic_templates/LtR2h4b1">variadic templates</a> (parameter pack) in C++ over the C-style variadic function due to a lower risk of misuse.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a>
</p>
<h3>In Fortran</h3>
<p>Since the Fortran 90 revision, <a href="/facts/Fortran/m1KqjcMU">Fortran</a> functions or subroutines can accept optional arguments:<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> the argument list is still fixed, but the ones that have the optional attribute can be omitted in the function/subroutine call. The intrinsic function present() can be used to detect the presence of an optional argument. The optional arguments can appear anywhere in the argument list. 
</p>
program test
implicit none

real :: x
    
    !> all arguments are passed:
    call foo( 1, 2, 3.0, 4, x )
    !< outputs 1 \ 2 \ 3.0 \ 4 \ 6.0 (the "\" denotes a newline)
    
    !> the last 2 arguments are omitted:
    call foo( 1, 2, 3.0 )
    !< outputs 1 \ 2 \ 3.0
    
    !> the 2nd and 4th arguments are omitted: the arguments that are positioned after 
    !> an omitted argument must be passed with a keyword:
    call foo( 1, c=3.0, e=x ) 
    !< outputs 1 \ 3.0 \ 6.0
    
    !> alternatively, the Fortran 2023 revision has introduced the .NIL. pseudo constant
    !> to denote an omitted argument
    call foo( 1, .NIL., 3.0, .NIL., x )
    !< outputs 1 \ 3.0 \ 6.0

contains

!> the subroutine foo() has 2 mandatory and 3 optional arguments
    subroutine foo( a, b, c, d, e )
        integer, intent(in)            :: a 
        integer, intent(in),  optional :: b
        real,    intent(in)            :: c
        integer, intent(in),  optional :: d
        real,    intent(out), optional :: e
        
        print*, a
        if (present(b)) print*, b 
        print*, c
        if (present(d)) print*, d
        if (present(e)) then
            e = 2*c
            print*, c
        end if
    end subroutine

end program

<p>Output:
</p>
The sum of [1 2] is 3 
The sum of [1 2 3] is 6 
The sum of [1 2 3 4] is 10

<h3>In Go</h3>
<p>Variadic functions in <a href="/facts/Go_(programming_language)/oWlsmAFJ">Go</a> can be called with any number of trailing arguments.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> fmt.Println is a common variadic function; it uses an empty interface as a catch-all type.
</p>
package main

import "fmt"

// This variadic function takes an arbitrary number of ints as arguments.
func sum(nums ...int) {
	fmt.Print("The sum of ", nums) // Also a variadic function.
	total := 0
	for _, num := range nums {
		total += num
	}
	fmt.Println(" is", total) // Also a variadic function.
}

func main() {
	// Variadic functions can be called in the usual way with individual
	// arguments.
	sum(1, 2)  // "The sum of [1 2] is 3"
	sum(1, 2, 3) // "The sum of [1 2 3] is 6"

// If you already have multiple args in a slice, apply them to a variadic
	// function using func(slice...) like this.
	nums := []int{1, 2, 3, 4}
	sum(nums...) // "The sum of [1 2 3 4] is 10"
}

<p>Output:
</p>
The sum of [1 2] is 3 
The sum of [1 2 3] is 6 
The sum of [1 2 3 4] is 10

<h3>In Java</h3>
<p>As with C#, the Object type in <a href="/facts/Java_(programming_language)/9ScgFyAL">Java</a> is available as a catch-all.
</p>
public class Program {
    // Variadic methods store any additional arguments they receive in an array.
    // Consequentially, `printArgs` is actually a method with one parameter: a
    // variable-length array of `String`s.
    private static void printArgs(String... strings) {
        for (String string : strings) {
            System.out.println(string);
        }
    }

public static void main(String[] args) {
        printArgs("hello");          // short for printArgs(["hello"])
        printArgs("hello", "world"); // short for printArgs(["hello", "world"])
    }
}

<h3>In JavaScript</h3>
<p><a href="/facts/JavaScript/XhhIIEsl">JavaScript</a> does not care about types of variadic arguments.
</p>
function sum(...numbers) {
    return numbers.reduce((a, b) => a + b, 0);
}

console.log(sum(1, 2, 3)); // 6
console.log(sum(3, 2));    // 5
console.log(sum());        // 0

<p>It's also possible to create a variadic function using the arguments object, although it is only usable with functions created with the function keyword.
</p>
function sum() {
    return Array.prototype.reduce.call(arguments, (a, b) => a + b, 0);
}

console.log(sum(1, 2, 3)); // 6
console.log(sum(3, 2));    // 5
console.log(sum());        // 0

<h3>In <a href="/facts/Lua_(programming_language)/xkBCgta0">Lua</a></h3>
<p><a href="/facts/Lua_(programming_language)/xkBCgta0">Lua</a> functions may pass varargs to other functions the same way as other values using the return keyword. tables can be passed into variadic functions by using, in Lua version 5.2 or higher<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> table.unpack, or Lua 5.1 or lower<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> unpack. Varargs can be used as a table by constructing a table with the vararg as a value.</p>function sum(...) --... designates varargs
   local sum=0
   for _,v in pairs({...}) do --creating a table with a varargs is the same as creating one with standard values
      sum=sum+v
   end
   return sum
end

values={1,2,3,4}
sum(5,table.unpack(values)) --returns 15. table.unpack should go after any other arguments, otherwise not all values will be passed into the function.

function add5(...)
  return ...+5 --this is incorrect usage of varargs, and will only return the first value provided
end

entries={}
function process_entries()
   local processed={}
   for i,v in pairs(entries) do
      processed[i]=v --placeholder processing code
   end
   return table.unpack(processed) --returns all entries in a way that can be used as a vararg
end

print(process_entries()) --the print function takes all varargs and writes them to stdout separated by newlines

<h3>In Pascal</h3>
<p><a href="/facts/Pascal_(programming_language)/b3yvp8bF">Pascal</a> is standardized by <a href="/facts/International_Organization_for_Standardization/IacYR7Yg">ISO</a> standards 7185 (“Standard Pascal”) and 10206 (“Extended Pascal”).
Neither standardized form of Pascal supports variadic routines, <i>except</i> for certain <a href="/facts/Intrinsic_function/r0re5n09">built-in routines</a> (read/readLn and write/writeLn, and additionally in EP readStr/writeStr).
</p><p>Nonetheless, <i>dialects</i> of Pascal implement mechanisms <i>resembling</i> variadic routines.
<a href="/facts/Delphi_(programming_language)/sUFUXQ8r">Delphi</a> defines an array of const data type that may be associated with the <i>last</i> <a href="/facts/Formal_parameter/LcuLbbSq">formal parameter</a>.
Within the routine definition the array of const is an array of TVarRec, an <a href="/facts/Array_(data_type)/gHJJ3XPw">array</a> of <a href="/facts/Variant_record/uMFenvCQ">variant records</a>.<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a>
The VType member of the aforementioned record data type allows inspection of the argument’s data type and subsequent appropriate handling.
The <a href="/facts/Free_Pascal_Compiler/kmGChqAg">Free Pascal Compiler</a> supports Delphi’s variadic routines, too.<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a>
</p><p>This implementation, however, technically requires a <i>single</i> argument, that is an array.
Pascal imposes the restriction that arrays need to be homogenous.
This requirement is circumvented by utilizing a variant record.
The <a href="/facts/GNU_Pascal/lwr1HC0g">GNU Pascal</a> defines a real variadic formal parameter specification using an ellipsis (...), but as of 2022 no portable mechanism to use such has been defined.<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a>
</p><p>Both GNU Pascal and FreePascal allow externally declared functions to use a variadic formal parameter specification using an ellipsis (...).
</p>
<h3>In PHP</h3>
<p><a href="/facts/PHP/02Lfe6RM">PHP</a> does not care about types of variadic arguments unless the argument is typed.
</p>
function sum(...$nums): int
{
    return array_sum($nums);
}

echo sum(1, 2, 3); // 6

<p>And typed variadic arguments:
</p>
function sum(int ...$nums): int
{
    return array_sum($nums);
}

echo sum(1, 'a', 3); // TypeError: Argument 2 passed to sum() must be of the type int (since PHP 7.3)

<h3>In Python</h3>
<p><a href="/facts/Python_(programming_language)/YbuGqofa">Python</a> does not care about types of variadic arguments.
</p>
def foo(a, b, *args):
    print(args)  # args is a tuple (immutable sequence).

foo(1, 2) # ()
foo(1, 2, 3) # (3,)
foo(1, 2, 3, "hello") # (3, "hello")

<p>Keyword arguments can be stored in a dictionary, e.g. def bar(*args, **kwargs).
</p>
<h3>In Raku</h3>
<p>In <a href="/facts/Raku_(programming_language)/9eYW7vRJ">Raku</a>, the type of parameters that create variadic functions are known as <i>slurpy</i> array parameters and they're classified into three groups:
</p>
<h4>Flattened slurpy</h4>
<p>These parameters are declared with a single asterisk (*) and they flatten arguments by dissolving one or more layers of elements that can be iterated over (i.e, <a href="https://docs.perl6.org/type/Iterable">Iterables</a>).
</p>
sub foo($a, $b, *@args) {
    say @args.perl;
}

foo(1, 2)                  # []
foo(1, 2, 3)               # [3]
foo(1, 2, 3, "hello")      # [3 "hello"]
foo(1, 2, 3, [4, 5], [6]); # [3, 4, 5, 6]

<h4>Unflattened slurpy</h4>
<p>These parameters are declared with two asterisks (**) and they do not flatten any iterable arguments within the list, but keep the arguments more or less as-is:
</p>
sub bar($a, $b, **@args) {
    say @args.perl;
}

bar(1, 2);                 # []
bar(1, 2, 3);              # [3]
bar(1, 2, 3, "hello");     # [3 "hello"]
bar(1, 2, 3, [4, 5], [6]); # [3, [4, 5], [6]]

<h4>Contextual slurpy</h4>
<p>These parameters are declared with a plus (+) sign and they apply the <i>"<a href="https://docs.perl6.org/language/functions#Slurpy_conventions">single argument rule</a>"</i>, which decides how to handle the slurpy argument based upon context. Simply put, if only a single argument is passed and that argument is iterable, that argument is used to fill the slurpy parameter array. In any other case, +@ works like **@ (i.e., unflattened slurpy).
</p>
sub zaz($a, $b, +@args) {
    say @args.perl;
}

zaz(1, 2);                 # []
zaz(1, 2, 3);              # [3]
zaz(1, 2, 3, "hello");     # [3 "hello"]
zaz(1, 2, [4, 5]);         # [4, 5], single argument fills up array
zaz(1, 2, 3, [4, 5]);      # [3, [4, 5]], behaving as **@
zaz(1, 2, 3, [4, 5], [6]); # [3, [4, 5], [6]], behaving as **@

<h3>In Ruby</h3>
<p><a href="/facts/Ruby_(programming_language)/BeYSaPSR">Ruby</a> does not care about types of variadic arguments.
</p>
def foo(*args)
  print args
end

foo(1)
# prints `[1]=> nil`

foo(1, 2)
# prints `[1, 2]=> nil`

<h3>In Rust</h3>
<p><a href="/facts/Rust_(programming_language)/8JNMV19F">Rust</a> does not support variadic arguments in functions. Instead, it uses <a href="/facts/Macro_(computer_science)/7abAsm1o">macros</a>.<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a>
</p>
macro_rules! calculate {
    // The pattern for a single `eval`
    (eval $e:expr) => {{
        {
            let val: usize = $e; // Force types to be integers
            println!("{} = {}", stringify!{$e}, val);
        }
    }};

// Decompose multiple `eval`s recursively
    (eval $e:expr, $(eval $es:expr),+) => {{
        calculate! { eval $e }
        calculate! { $(eval $es),+ }
    }};
}

fn main() {
    calculate! { // Look ma! Variadic `calculate!`!
        eval 1 + 2,
        eval 3 + 4,
        eval (2 * 3) + 1
    }
}

<p>Rust is able to interact with C's variadic system via a c_variadic feature switch. As with other C interfaces, the system is considered unsafe to Rust.<a class="footnote-ref" id="fnref:16" href="#fn:16"><sup>16</sup></a>
</p>
<h3>In Scala</h3>
object Program {
  // Variadic methods store any additional arguments they receive in an array.
  // Consequentially, `printArgs` is actually a method with one parameter: a
  // variable-length array of `String`s.
  private def printArgs(strings: String*): Unit = {
    strings.foreach(println)
  }

def main(args: Array[String]): Unit = {
    printArgs("hello");          // short for printArgs(["hello"])
    printArgs("hello", "world"); // short for printArgs(["hello", "world"])
  }
}

<h3>In Swift</h3>
<p><a href="/facts/Swift_(programming_language)/A7qHQC32">Swift</a> cares about the type of variadic arguments, but the catch-all Any type is available.
</p>
func greet(timeOfTheDay: String, names: String...) {
    // here, names is [String]
    
    print("Looks like we have \(names.count) people")
    
    for name in names {
        print("Hello \(name), good \(timeOfTheDay)")
    }
}

greet(timeOfTheDay: "morning", names: "Joseph", "Clara", "William", "Maria")

// Output:
// Looks like we have 4 people
// Hello Joseph, good morning
// Hello Clara, good morning
// Hello William, good morning
// Hello Maria, good morning

<h3>In Tcl</h3>
<p>A <a href="/facts/Tcl/s7fbKYtR">Tcl</a> procedure or lambda is variadic when its last argument is args: this will contain a list (possibly empty) of all the remaining arguments. This pattern is common in many other procedure-like methods.<a class="footnote-ref" id="fnref:17" href="#fn:17"><sup>17</sup></a><a class="footnote-ref" id="fnref:18" href="#fn:18"><sup>18</sup></a>
</p>
proc greet {timeOfTheDay args} {
    puts "Looks like we have [llength $args] people"

foreach name $args {
        puts "Hello $name, good $timeOfTheDay"
    }
}

greet "morning" "Joseph" "Clara" "William" "Maria"

# Output:
# Looks like we have 4 people
# Hello Joseph, good morning
# Hello Clara, good morning
# Hello William, good morning
# Hello Maria, good morning

<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Java_syntax/94FIPWBa">Varargs in Java programming language</a></li>
<li><a href="/facts/Variadic_macro/T0PvNWp1">Variadic macro</a> (C programming language)</li>
<li><a href="/facts/Variadic_template/LtR2h4b1">Variadic template</a></li></ul>
<h2 id="notes">Notes</h2>

<h2 id="external-links">External links</h2>
<ul><li><a href="http://rosettacode.org/wiki/Variadic_function">Variadic function</a>. <a href="/facts/Rosetta_Code/HAN5rwmX">Rosetta Code</a> task showing the implementation of variadic functions in over 120 programming languages.</li>
<li><a href="https://web.archive.org/web/20070927215504/http://www.codeproject.com/cpp/argfunctions.asp?df=100&forumid=15556&exp=0&select=503481">Variable Argument Functions</a> — A tutorial on Variable Argument Functions for C++</li>
<li><a href="https://www.gnu.org/software/hello/manual/libc/Variadic-Functions.html">GNU libc manual</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Henry S. Leonard and H. N. Goodman, A calculus of individuals. Abstract of a talk given at the Second Meeting of the Association for Symbolic Logic, held in Cambridge MA on December 28–30, 1936, [1], Journal of Symbolic Logic 2(1) 1937, 63. <a href="https://www.jstor.org/stable/2268861" target="_blank">https://www.jstor.org/stable/2268861</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Klemens, Ben (2014). 21st Century C: C Tips from the New School. O'Reilly Media, Inc. p. 224. ISBN 978-1491904442. <a href="978-1491904442" target="_blank">978-1491904442</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>CLP (H): Constraint Logic Programming for Hedges <a href="https://arxiv.org/abs/1503.00336" target="_blank">https://arxiv.org/abs/1503.00336</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>"<cstdarg> (stdarg.h) - C++ Reference". www.cplusplus.com. <a href="http://www.cplusplus.com/reference/clibrary/cstdarg/" target="_blank">http://www.cplusplus.com/reference/clibrary/cstdarg/</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
<li id="fn:5"><p>Making the named parameter optional was needed since there was no way to specify a function taking an unspecified number of arguments in C23 after the removal of K&R style function definitions. Since C++ was already using this syntax for the same purpose, this change was also a way to increase compatibility between the languages.[5] <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li>
<li id="fn:6"><p>Gilding, Alex; Meneide, JeanHeyd (2022-04-15). "WG14-N2975 : Relax requirements for variadic parameter lists, v3" (PDF). <a href="https://open-std.org/JTC1/SC22/WG14/www/docs/n2975.pdf" target="_blank">https://open-std.org/JTC1/SC22/WG14/www/docs/n2975.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li>
<li id="fn:7"><p>"DCL50-CPP. Do not define a C-style variadic function". <a href="https://wiki.sei.cmu.edu/confluence/display/cplusplus/DCL50-CPP" target="_blank">https://wiki.sei.cmu.edu/confluence/display/cplusplus/DCL50-CPP</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li>
<li id="fn:8"><p>"Optional Arguments". Intel. Retrieved 2025-03-18. <a href="https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2023-0/optional-arguments.html" target="_blank">https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2023-0/optional-arguments.html</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li>
<li id="fn:9"><p>"Go by Example: Variadic Functions". <a href="https://gobyexample.com/variadic-functions" target="_blank">https://gobyexample.com/variadic-functions</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li>
<li id="fn:10"><p>"Lua 5.2 Reference Manual". www.lua.org. Retrieved 2023-02-05. <a href="https://www.lua.org/manual/5.2/manual.html#pdf-table.unpack" target="_blank">https://www.lua.org/manual/5.2/manual.html#pdf-table.unpack</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li>
<li id="fn:11"><p>"Lua 5.1 Reference Manual". www.lua.org. Retrieved 2023-02-05. <a href="https://www.lua.org/manual/5.1/manual.html#pdf-unpack" target="_blank">https://www.lua.org/manual/5.1/manual.html#pdf-unpack</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li>
<li id="fn:12"><p>"Parameters (Delphi)". Retrieved 2023-08-28. <a href="https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Parameters_(Delphi)#Variant_Open_Array_Parameters" target="_blank">https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Parameters_(Delphi)#Variant_Open_Array_Parameters</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li>
<li id="fn:13"><p>"Free Pascal - Reference guide". Retrieved 2023-08-28. <a href="https://www.freepascal.org/docs-html/3.2.0/ref/refsu68.html" target="_blank">https://www.freepascal.org/docs-html/3.2.0/ref/refsu68.html</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li>
<li id="fn:14"><p>"The GNU Pascal Manual". Retrieved 2023-08-28. <a href="https://www.gnu-pascal.de/gpc/Special-Parameters.html" target="_blank">https://www.gnu-pascal.de/gpc/Special-Parameters.html</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li>
<li id="fn:15"><p>"Variadics". Rust By Example. <a href="https://doc.rust-lang.org/rust-by-example/macros/variadics.html" target="_blank">https://doc.rust-lang.org/rust-by-example/macros/variadics.html</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li>
<li id="fn:16"><p>"2137-variadic". The Rust RFC Book. <a href="https://rust-lang.github.io/rfcs/2137-variadic.html" target="_blank">https://rust-lang.github.io/rfcs/2137-variadic.html</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></p></li>
<li id="fn:17"><p>"proc manual page". Tcl/Tk Documentation. <a href="https://www.tcl.tk/man/tcl/TclCmd/proc.html" target="_blank">https://www.tcl.tk/man/tcl/TclCmd/proc.html</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></p></li>
<li id="fn:18"><p>"args". Tcler's Wiki. <a href="https://wiki.tcl-lang.org/page/args" target="_blank">https://wiki.tcl-lang.org/page/args</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></p></li>
</ol>

Variadic function open-in-new

Variadic function