From: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org
Subject: [PATCH v2] fread.3: Explain that file position is moved after calling fread()/fwrite()
Date: Wed, 17 Jun 2020 00:15:20 +0200 [thread overview]
Message-ID: <20200616221520.21741-1-arkadiusz@drabczyk.org> (raw)
Corresponding manpage on FreeBSD already contains that information.
Signed-off-by: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
---
man3/fread.3 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/man3/fread.3 b/man3/fread.3
index 2dd7be9..2dcca9b 100644
--- a/man3/fread.3
+++ b/man3/fread.3
@@ -92,6 +92,9 @@ is 1.
If an error occurs, or the end of the file is reached,
the return value is a short item count (or zero).
.PP
+The file position indicator for the stream is advanced by the number
+of bytes successfully read or written.
+.PP
.BR fread ()
does not distinguish between end-of-file and error, and callers must use
.BR feof (3)
--
2.9.0
next reply other threads:[~2020-06-16 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 22:15 Arkadiusz Drabczyk [this message]
2020-06-19 12:28 ` [PATCH v2] fread.3: Explain that file position is moved after calling fread()/fwrite() Michael Kerrisk (man-pages)
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=20200616221520.21741-1-arkadiusz@drabczyk.org \
--to=arkadiusz@drabczyk.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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: 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;
as well as URLs for NNTP newsgroup(s).