public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug stdio/1190] fgetc()/fread() behaviour is not POSIX compliant Date: Thu, 13 Sep 2012 13:52:00 -0000 [thread overview] Message-ID: <bug-1190-131-I95KkmfjSI@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-1190-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=1190 --- Comment #13 from Siddhesh Poyarekar <siddhesh at redhat dot com> 2012-09-13 13:52:06 UTC --- The change is quite simple, but a comment in fileops.c says that this behaviour is retained for sysv compatibility: ... int _IO_new_file_underflow (fp) _IO_FILE *fp; { _IO_ssize_t count; #if 0 /* SysV does not make this test; take it out for compatibility */ if (fp->_flags & _IO_EOF_SEEN) return (EOF); #endif ... I'm not sure if this is valid anymore, so I'll try to find out what the current status is, unless someone here already knows the answer. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-09-13 13:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-1190-131@http.sourceware.org/bugzilla/> 2011-10-27 2:08 ` [Bug libc/1190] " bugdal at aerifal dot cx 2011-10-27 2:08 ` bugdal at aerifal dot cx 2011-11-04 18:31 ` gotom at debian dot or.jp 2012-02-21 1:33 ` [Bug stdio/1190] " jsm28 at gcc dot gnu.org 2012-02-21 2:01 ` funtoos at yahoo dot com 2012-03-17 20:34 ` bugdal at aerifal dot cx 2012-03-18 14:23 ` jsm28 at gcc dot gnu.org 2012-09-13 13:33 ` siddhesh at redhat dot com 2012-09-13 13:52 ` siddhesh at redhat dot com [this message] 2012-09-13 14:15 ` siddhesh at redhat dot com 2022-09-23 5:25 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1190-131-I95KkmfjSI@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).