This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/1190] fgetc()/fread() behaviour is not POSIX compliant
- From: "funtoos at yahoo dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 30 Sep 2005 20:50:16 -0000
- Subject: [Bug libc/1190] fgetc()/fread() behaviour is not POSIX compliant
- References: <20050810161252.1190.funtoos@yahoo.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From funtoos at yahoo dot com 2005-09-30 20:50 -------
its a simple thing. fgetc() needs to return EOF if EOF is what the last call had
returned and is set on the stream, even though there is new data ready to be
read. EOF should be explicitly cleared (by the programmer) before the next call
to fgetc() is made by the programmer. This is a simple POSIX compliance
requirement as per the links I provided. What do we need a test case for? Are
you saying that the behaviour reported in the example is not the current
behaviour of glibc?
--
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
http://sourceware.org/bugzilla/show_bug.cgi?id=1190
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.