Date: Sat, 4 Apr 2009 15:00:07 GMT From: Jilles Tjoelker <jilles@stack.nl> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/108118: [libc] files should not cache their EOF status Message-ID: <200904041500.n34F077G002279@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/108118; it has been noted by GNATS. From: Jilles Tjoelker <jilles@stack.nl> To: bug-followup@FreeBSD.org, twschulz@trolltech.com, freebsd-standards@freebsd.org Cc: Subject: Re: bin/108118: [libc] files should not cache their EOF status Date: Sat, 4 Apr 2009 16:56:29 +0200 The way I read POSIX, FreeBSD's current behaviour seems correct. Calling fread(3) is equivalent to calling fgetc(3) an appropriate number of times, and fgetc(3) shall fail if the end-of-file indicator is set for the stream, even if data is available on the underlying file. Apparently, POSIX aligns with the C standard here; System V tradition is not to check the end-of-file indicator here. Both src/lib/libc/stdio/refill.c (__srefill()) and Solaris fgetc(3) manpage agree about this. -- Jilles Tjoelker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200904041500.n34F077G002279>