Message-ID: <393CF26B.666BEA87@softhome.net> Date: Tue, 06 Jun 2000 15:45:31 +0300 From: Laurynas Biveinis X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: ANSI C and stdio.h References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hans-Bernhard Broeker wrote: > Actually, the only reason I can see for importing the definition of > va_list into is that the compiler cannot accept that header, > without it. Code that actually does use vfprintf() & friends will always > have to #include to be portable. DJGPP allows this kind of unportable code, that's the reason we won't fix it (now?) > The remaining question is whether the *name* of the va_list type, as > defined and used in may have to be moved away from the public > name space, i.e. renamed to something like > > __dj_va_list > > with containing the same use as and > an additional > > typedef __dj_va_list va_list; > > to provide the 'official' name of that type. That was the key question from the beginning and this was exactly the solution I was thinking about. Laurynas