From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215097] Example in getpwnam_r man page compares size_t variable to -1
Date: Mon, 22 Nov 2021 13:22:27 +0000 [thread overview]
Message-ID: <bug-215097-11311-lmX7TaUEV7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215097-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215097
--- Comment #2 from Fabian (fabian@ritter-vogt.de) ---
(In reply to Alejandro Colomar (man-pages) from comment #1)
> Yes, long (sysconf(3) uses that) or ssize_t (to indicate a size) seem better
> types. Which one do you prefer?
IMO using "long" makes the most sense. It's already used as the return value of
sysconf, while ssize_t has no direct relevance to the code.
> Also I noticed that sysconf(3) doesn't document _SC_GETPW_R_SIZE_MAX.
Oh, indeed!
--
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 prev parent reply other threads:[~2021-11-22 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 10:24 [Bug 215097] New: Example in getpwnam_r man page compares size_t variable to -1 bugzilla-daemon
2021-11-22 12:21 ` [Bug 215097] " bugzilla-daemon
2021-11-22 13:22 ` bugzilla-daemon [this message]
2021-11-23 11:46 ` 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-215097-11311-lmX7TaUEV7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox