Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"Harold Hunt" <huntharo AT msu DOT edu>
To:	"Danny Smith" <danny_r_smith_2001 AT yahoo DOT co DOT nz>
Cc:	"cygwin" <cygwin AT cygwin DOT com>
Subject:	RE: __STRICT_ANSI__
Date:	Thu, 17 May 2001 02:20:02 -0400
Message-ID:	<NHEELHJHHFKPMAEAFMFCEEFLCFAA.huntharo@msu.edu>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To:	<20010516233855.29403.qmail@web6405.mail.yahoo.com>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

Danny,

> ANSI portable code, don't use them.  __STRICT_ANSI__ is doing its job
> correctly, thank you very much.

Yup, you're right.  If you pass -ansi to gcc *and* you define __USE_POSIX,
then you surely should not be able to use fdopen or fileno.  Wait a
minute...

I am more inclined to believe that the standard lib on Linux is more correct
than newlib.  Then again, what is correct?  The standard that everyone has
been using for years or the "standard"?  I have no idea...

On a side note, I couldn't find anywhere that XFree86 defines
__STRICT_ANSI__; rather, __STRICT_ANSI__ seems to be a side effect of
passing -ansi to gcc...

Harold


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -