Message-ID:	<394E36F4.4180768E@softhome.net>
Date:	Mon, 19 Jun 2000 17:06:28 +0200
From:	Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer:	Mozilla 4.73 [en] (Win98; U)
X-Accept-Language:	lt,en
MIME-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC:	djgpp-workers AT delorie DOT com
Subject:	Re: Patch: new GCC builtins for stdarg.h/varargs.h
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000619173337 DOT 27216Q-100000 AT is>
Reply-To:	djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> 
> On Sun, 18 Jun 2000, Laurynas Biveinis wrote:
> 
> > +@cindex stdarg.h{, GCC 2.96}
> > +@cindex varargs.h{, GCC 2.96}
> > +When used together with GCC 2.96 or later, va_list facilities
> > +in <stdarg.h> and <varargs.h> are implemented using new
> > +builtins from GCC 2.96.
> 
> I think this warrants @findex entries for the va_* macros, not only
> for the headers they appear in.  In fact, having the index entries for
> the macros is IMHO much more important, since that's how people are
> likely to look for those changes.
> 
> Also, please use either @code{<stdio.h>} or @file{stdio.h}.

Does this one look better?

Laurynas

Index: wc204.txi
===================================================================
RCS file: /cvs/djgpp/djgpp/src/docs/kb/wc204.txi,v
retrieving revision 1.4
diff -u -r1.4 wc204.txi
--- wc204.txi	2000/06/19 09:16:43	1.4
+++ wc204.txi	2000/06/19 15:02:19
@@ -8,8 +8,15 @@
 
 @cindex stdarg DOT h AT r{, GCC 2.96}
 @cindex varargs DOT h AT r{, GCC 2.96}
+@findex va_list AT r{, GCC 2.96}
+@findex va_start AT r{, GCC 2.96}
+@findex va_arg AT r{, GCC 2.96}
+@findex va_end AT r{, GCC 2.96}
+@findex va_alist AT r{, GCC 2.96}
+@findex va_dcl AT r{, GCC 2.96}
+
 When used together with GCC 2.96 or later, va_list facilities
-in <stdarg.h> and <varargs.h> are implemented using new
+in @file{stdarg.h} and @file{varargs.h} are implemented using new
 builtins from GCC 2.96.
 
 @findex fsdb AT r{, check for EXE extension}

- Raw text -