From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 213341] New: Man Page for ferror/feof has bad information in "Return Value" Section
Date: Fri, 04 Jun 2021 22:37:41 +0000 [thread overview]
Message-ID: <bug-213341-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213341
URL: https://man7.org/linux/man-pages/man3/ferror.3.html
Bug ID: 213341
Summary: Man Page for ferror/feof has bad information in
"Return Value" Section
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: low
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: vulkur@protonmail.com
Regression: No
Within the man page for ferror and feof, there is a description for the return
value of feof twice. The second description is for ferror.
>This:
> The feof() function returns nonzero if the end-of-file indicator
> is set for stream; otherwise, it returns zero.
>
> The feof() function returns nonzero if the error indicator is set
> for stream; otherwise, it returns zero.
>Should be this:
> The feof() function returns nonzero if the end-of-file indicator
> is set for stream; otherwise, it returns zero.
>
> The ferror() function returns nonzero if the error indicator is set
> for stream; otherwise, it returns zero.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-06-04 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 22:37 bugzilla-daemon [this message]
2021-06-04 22:49 ` [Bug 213341] Man Page for ferror/feof has bad information in "Return Value" Section bugzilla-daemon
2021-06-07 14:31 ` bugzilla-daemon
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-213341-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.