| stdarg.3 (6cec9cad762b6476313fb1f8e931a1647822db6b) | stdarg.3 (757a04bf824d8d12f970ce79b5c816b2c3a571e7) |
|---|---|
| 1.\" Copyright (c) 1990, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" This code is derived from software contributed to Berkeley by 5.\" the American National Standards Committee X3, on Information 6.\" Processing Systems. 7.\" 8.\" Redistribution and use in source and binary forms, with or without --- 18 unchanged lines hidden (view full) --- 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)stdarg.3 8.1 (Berkeley) 6/5/93 33.\" $FreeBSD$ 34.\" | 1.\" Copyright (c) 1990, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" This code is derived from software contributed to Berkeley by 5.\" the American National Standards Committee X3, on Information 6.\" Processing Systems. 7.\" 8.\" Redistribution and use in source and binary forms, with or without --- 18 unchanged lines hidden (view full) --- 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)stdarg.3 8.1 (Berkeley) 6/5/93 33.\" $FreeBSD$ 34.\" |
| 35.Dd October 25, 2002 | 35.Dd February 25, 2020 |
| 36.Dt STDARG 3 37.Os 38.Sh NAME 39.Nm stdarg 40.Nd variable argument lists 41.Sh SYNOPSIS 42.In stdarg.h 43.Ft void --- 168 unchanged lines hidden (view full) --- 212The 213.Fn va_start , 214.Fn va_arg , 215.Fn va_copy , 216and 217.Fn va_end 218macros conform to 219.St -isoC-99 . | 36.Dt STDARG 3 37.Os 38.Sh NAME 39.Nm stdarg 40.Nd variable argument lists 41.Sh SYNOPSIS 42.In stdarg.h 43.Ft void --- 168 unchanged lines hidden (view full) --- 212The 213.Fn va_start , 214.Fn va_arg , 215.Fn va_copy , 216and 217.Fn va_end 218macros conform to 219.St -isoC-99 . |
| 220.Sh HISTORY 221The 222.Fn va_start , 223.Fn va_arg 224and 225.Fn va_end 226macros were introduced in 227.St -ansiC . 228The 229.Fn va_copy 230macro was introduced in 231.St -isoC-99 . |
|
| 220.Sh BUGS 221Unlike the 222.Em varargs 223macros, the 224.Nm 225macros do not permit programmers to 226code a function with no fixed arguments. 227This problem generates work mainly when converting 228.Em varargs 229code to 230.Nm 231code, 232but it also creates difficulties for variadic functions that 233wish to pass all of their arguments on to a function 234that takes a 235.Em va_list 236argument, such as 237.Xr vfprintf 3 . | 232.Sh BUGS 233Unlike the 234.Em varargs 235macros, the 236.Nm 237macros do not permit programmers to 238code a function with no fixed arguments. 239This problem generates work mainly when converting 240.Em varargs 241code to 242.Nm 243code, 244but it also creates difficulties for variadic functions that 245wish to pass all of their arguments on to a function 246that takes a 247.Em va_list 248argument, such as 249.Xr vfprintf 3 . |