From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 91931] New: fflush(3) is misleading about input streams
Date: Fri, 23 Jan 2015 16:15:25 +0000 [thread overview]
Message-ID: <bug-91931-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=91931
Bug ID: 91931
Summary: fflush(3) is misleading about input streams
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
Reporter: cubbi-+Aw+eGX9mmUAvxtiuMwx3w@public.gmane.org
Regression: No
Current fflush(3) claims that
"For input streams, fflush() discards any buffered data that has been fetched
from the underlying file, but has not been consumed by the application."
While technically true (assuming 'file' implies seekable device), this is
incomplete: flushing an input stream associated with a non-seekable device,
such as the terminal input, does nothing (the update to fp->_IO_read_end at
libio/fileops.c:872 does not happen due to ESPIPE from lseek)
There have been enough confused beginner posts to various internet forums
asking why flushing stdin doesn't work on Linux. I believe it is worth making
the man page more explicit. At the very least, it should begin that sentence
with "For input streams associated with seekable devices", or perhaps it should
mention the unfortunately popular use case fflush(stdin) explicitly.
On a very minor note, fflush(3) also claims that
"The standards do not specify the behavior for input streams"
This is no longer precisely correct; POSIX specifies behavior for seekable
input streams to move fileno's offset to match FILE's offset and undo all
ungetc's: http://pubs.opengroup.org/onlinepubs/9699919799/functions/fflush.html
and glibc conforms to that (or tries to,
https://sourceware.org/bugzilla/show_bug.cgi?id=5994 is still open)
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-01-23 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 16:15 bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
[not found] ` <bug-91931-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2015-01-25 19:53 ` [Bug 91931] fflush(3) is misleading about input streams bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2015-01-27 4:35 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2015-01-28 8:31 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2015-01-28 8:33 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
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-91931-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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: link
Be 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