From 4535cd55e2fc005afe0cf549a767ae60d55b17dd Mon Sep 17 00:00:00 2001 From: Joseph Myers Date: Wed, 21 Mar 2012 17:52:19 +0000 Subject: [PATCH] Don't document varargs.h. --- ChangeLog | 6 ++++++ manual/lang.texi | 66 -------------------------------------------------------- 2 files changed, 6 insertions(+), 66 deletions(-) diff --git a/ChangeLog b/ChangeLog index e8b43e4..b1822df 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2012-03-21 Joseph Myers + + * manual/lang.texi (Old Varargs): Remove section. + (How Variadic): Update menu. + (va_start): Do not mention varargs.h. + 2012-03-21 Thomas Schwinge Joseph Myers diff --git a/manual/lang.texi b/manual/lang.texi index 6cb7371..baaccaa 100644 --- a/manual/lang.texi +++ b/manual/lang.texi @@ -229,7 +229,6 @@ additional variable arguments. @xref{Calling Variadics}. variable arguments functions. * Argument Macros:: Detailed specification of the macros for accessing variable arguments. -* Old Varargs:: The pre-ISO way of defining variadic functions. @end menu @node Variadic Prototypes @@ -427,9 +426,6 @@ The type @code{va_list} is used for argument pointer variables. This macro initializes the argument pointer variable @var{ap} to point to the first of the optional arguments of the current function; @var{last-required} must be the last required argument to the function. - -@xref{Old Varargs}, for an alternate definition of @code{va_start} -found in the header file @file{varargs.h}. @end deftypefn @comment stdarg.h @@ -511,68 +507,6 @@ arguments facility. @include add.c.texi @end smallexample -@node Old Varargs -@subsubsection Old-Style Variadic Functions - -@pindex varargs.h -Before @w{ISO C}, programmers used a slightly different facility for -writing variadic functions. The GNU C compiler still supports it; -currently, it is more portable than the @w{ISO C} facility, since support -for @w{ISO C} is still not universal. The header file which defines the -old-fashioned variadic facility is called @file{varargs.h}. - -Using @file{varargs.h} is almost the same as using @file{stdarg.h}. -There is no difference in how you call a variadic function; -see @ref{Calling Variadics}. The only difference is in how you define -them. First of all, you must use old-style non-prototype syntax, like -this: - -@smallexample -tree -build (va_alist) - va_dcl -@{ -@end smallexample - -Secondly, you must give @code{va_start} only one argument, like this: - -@smallexample - va_list p; - va_start (p); -@end smallexample - -These are the special macros used for defining old-style variadic -functions: - -@comment varargs.h -@comment Unix -@deffn Macro va_alist -This macro stands for the argument name list required in a variadic -function. -@end deffn - -@comment varargs.h -@comment Unix -@deffn Macro va_dcl -This macro declares the implicit argument or arguments for a variadic -function. -@end deffn - -@comment varargs.h -@comment Unix -@deftypefn {Macro} void va_start (va_list @var{ap}) -This macro, as defined in @file{varargs.h}, initializes the argument -pointer variable @var{ap} to point to the first argument of the current -function. -@end deftypefn - -The other argument macros, @code{va_arg} and @code{va_end}, are the same -in @file{varargs.h} as in @file{stdarg.h}; see @ref{Argument Macros}, for -details. - -It does not work to include both @file{varargs.h} and @file{stdarg.h} in -the same compilation; they define @code{va_start} in conflicting ways. - @node Null Pointer Constant @section Null Pointer Constant @cindex null pointer constant -- 2.7.4