Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 8 Mar 2004 09:06:01 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.5.1 fgetc returns no error for bad file descriptor Message-ID: <20040308140601.GC30618@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Reply-To: cygwin AT cygwin DOT com Note-from-DJ: This may be spam On Mon, Mar 08, 2004 at 08:11:37PM +0000, Ghanshyam wrote: >The 9th assertion of fgetc in "IEEE std 2003.1-1992 Test Methods for >Measuring Conformance to Posix-Part1 System Interface" document states: >When the stream pointer argument addresses a file descriptor that is >not open for reading, then a call to fgetc()returns a value of EOF and >sets errno to [EBADF]. The current implementation does not set any >errno. It says "No error". Since this is a simple thing to demonstrate, rather than have someone go to the effort of writing a test program to see if your assertion is correct, why not submit a test program which demonstrates the problem that you are allegedly seeing? You could even take the extra step of submitting a patch to fix this behavior. The code in question is in newlib. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/