Date: Mon, 10 Oct 2011 19:46:11 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: stdio.h: broken standard compliance.
Message-ID: <20111010234611.GB23672@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <203df9f173be7f13d23b3e7c0fc831c1@127.0.0.1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <203df9f173be7f13d23b3e7c0fc831c1@127.0.0.1>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mon, Oct 10, 2011 at 11:42:45AM -0700, Kaz Kylheku wrote:
>
>Corinna Vinschen writes:
>
>> > $ gcc -Wall -ansi -D_POSIX_C_SOURCE=2 posix-ansi.c
> ^^^^^
>> fileno and pclose are *not* ANSI functions. Therefore, if you define
>> -ansi, you get the below errors. The newlib headers have explicit
>> #ifndef __STRICT_ANSI__ guards around the non-ANSI definitions.
>
>(Could you use "reply all?" for discussions so the original
>person is included, but the mailing list is kept in the loop with a 
>CC?
>I had to dig your reply out of the online archives.)

The convention in this mailing list is that you read the mailing list.
Practically speaking, if you want help, it pays to comply with
convention rather than asking others to accommodate you.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple