Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: "Harold Hunt" To: "Danny Smith" Cc: "cygwin" Subject: RE: __STRICT_ANSI__ Date: Thu, 17 May 2001 02:20:02 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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