Date: Mon, 5 Jun 2000 16:07:32 -0400
Message-Id: <200006052007.QAA21663@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <200006051915.PAA04340@qnx.com> (alain@qnx.com)
Subject: Re: ANSI C and stdio.h
References:  <200006051915 DOT PAA04340 AT qnx DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Maybe it's me who got this backward or I've missed a couple of threads.

In DJGPP, stdio doesn't include stdlib.  It uses a djgpp-specific
header to get *just* va_list, the one thing needed to properly
prototype functions like vfprintf.  If you tried to use, say, va_start
with stdio but without stdarg, it would still fail.

> This is probably picknitting, because I doubt a portable application
> will call va_arg() without including <stdarg.h>

*That* won't work in DJGPP.

> > 1. Broken programs that work under DJGPP.
> > 
> > 2. Valid programs that break under DJGPP.
> 
> Yes, fine goals.  I just hope to make (1) work, you don't
> deviate too much from the std or carry a lot of baggages.

Right.  Avoiding #2 is certainly the higher priority.