Date: Mon, 5 Jun 2000 08:56:15 -0400
Message-Id: <200006051256.IAA25791@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <393B7081.DBD8EC8B@softhome.net> (message from Laurynas Biveinis
	on Mon, 05 Jun 2000 12:18:57 +0300)
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> <393AA7CF DOT 51E1DE11 AT softhome DOT net> <200006042012 DOT QAA08975 AT envy DOT delorie DOT com> <393B7081 DOT DBD8EC8B AT softhome DOT net>
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


> Will the requirement to include stdarg.h in order to use vprintf()
> count as problem?

If previous versions of djgpp didn't require it, that's a problem.

> IMHO there already is a problem - we encourage users to write
> unportable code.

No, we *allow* it, we don't *encourage* it.  I don't want to
gratuitously break existing code if we don't have to.

> Those sys/*.h headers are OK - they aren't covered by ANSI and they
> will continue 'just work' The number of affected ANSI headers is
> very limited.

They are covered by POSIX, so the same rules apply.