This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: manual: Update @standards for [__]va_copy.
- From: Zack Weinberg <zackw at panix dot com>
- To: Rical Jasan <ricaljasan at pacific dot net>, libc-alpha at sourceware dot org
- Cc: Joseph Myers <joseph at codesourcery dot com>, Carlos O'Donell <carlos at redhat dot com>, Michael Kerrisk <mtk dot manpages at gmail dot com>
- Date: Sat, 17 Jun 2017 09:59:50 -0400
- Subject: Re: manual: Update @standards for [__]va_copy.
- Authentication-results: sourceware.org; auth=none
- References: <20170617084202.4662-1-ricaljasan@pacific.net>
On 06/17/2017 04:42 AM, Rical Jasan wrote:
> There is question as to whether __va_copy should be documented in the
> glibc manual at all. Since users searching for *va_copy are likely to
> find this manual, and GCC doesn't document either, it is important we
> continue to provide some kind of reference.
Let's leave alone the question of whether we should document a GCC
extension for now.
This patch is OK with some additional wording adjustments: in the second
paragraph of the @deftypefn block, change "This macro" to
"@code{va_copy}", "@samp{gcc -ansi}" to "@samp{gcc -std=c90}", and "The
macro @code{__va_copy} is available as a GNU extension;" to "GCC
provides @code{__va_copy}, as an extension, in any standards mode."
Delete the clause beginning "before GCC 3.0", as I believe compilers
that old will no longer work with glibc's headers anyway.
zw