Message-ID: <393AA7CF.51E1DE11@softhome.net>
Date: Sun, 04 Jun 2000 22:02:39 +0300
From: Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com, Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Subject: Re: ANSI C and stdio.h
References: <3937DEA9 DOT 63606B27 AT softhome DOT net> <200006021918 DOT PAA03693 AT envy DOT delorie DOT com> <3938C1DE DOT E005BBA9 AT softhome DOT net> <200006030953 DOT MAA01306 AT alpha DOT netvision DOT net DOT il> <39394EC9 DOT 91B87484 AT softhome DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Laurynas Biveinis wrote:
> But this still does not clear things for me. Maybe I'll ask in
> comp.std.c

Here is the first reply I got there. This guy does not point
to the exact place to the standard, but he is one of the major
posters there. It seems we've got a problem there. If there
will be no other opinions in c.s.c, I'll make a patch for this
issue.

Douglas A. Gwyn wrote:
>Laurynas Biveinis wrote:
>> is it true that stdio.h cannot define va_list, although it
>> has to use it for vprintf() family prototypes? How should
>> those prototypes be written in this case?
>
>It is true that stdio.h cannot define va_list if the implementation
>is to conform to the C standard.  This is but one example of a
>general issue that implementors of standard headers need to deal
>with.  One solution is to have duplicate definitions of such
>things in the namespace reserved for implementation use, and use
>those where necessary:
>
>/* <stdio.h> excerpt: */
>#include <impldefs.h>   /* defines __va_list, among other things */
>extern int vprintf(const char *__format, __va_list __arg);

Laurynas