Message-ID:	<393B7081.DBD8EC8B@softhome.net>
Date:	Mon, 05 Jun 2000 12:18:57 +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
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>
Reply-To:	djgpp-workers AT delorie DOT com

DJ Delorie wrote:
> 
> > 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.
> 
> As long as any patch has absolutely *no* chance of causing problems.

Will the requirement to include stdarg.h in order to use vprintf() count
as problem? IMHO there already is a problem - we encourage users to
write unportable code. Their 'strictly ANSI' code will stop compiling
on other 'strictly ANSI' system.

> Standards aside, we've had a lot of luck with our headers and have
> gotten almost no FAQs about them due to obsessive standards
> compliance.  There are a number of headers that are this way (for
> example, sys/stat.h doesn't require sys/types.h) and I'd rather this
> continue working than cause problems for users in the name of
> "standards".

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.

Laurynas

- Raw text -