public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "minekpo1 at protonmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/31273] New: Custom Stream Hook Functions: fgetpos is said to have a whence argument
Date: Mon, 22 Jan 2024 17:47:46 +0000 [thread overview]
Message-ID: <bug-31273-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31273
Bug ID: 31273
Summary: Custom Stream Hook Functions: fgetpos is said to have
a whence argument
Product: glibc
Version: 2.40
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: manual
Assignee: unassigned at sourceware dot org
Reporter: minekpo1 at protonmail dot com
CC: mtk.manpages at gmail dot com
Target Milestone: ---
In section 12.21.2.2 Custom Stream Hook Functions, while describing the seeker
hook, the manual reads:
> For this function, the position and whence arguments are interpreted as for fgetpos; see Portable File-Position Functions.
However fgetpos does not have a whence argument, at least currently.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2024-01-22 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-31273-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).