From: Alejandro Colomar <alx@kernel.org>
To: Seth McDonald <sethmcmail@pm.me>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v1 12/15] man/man3type/id_t.3type: HISTORY: Mention change in datatypes of [pug]id_t(3type)
Date: Wed, 7 Jan 2026 08:55:28 +0100 [thread overview]
Message-ID: <aV4RGWzP3C9pbjI8@devuan> (raw)
In-Reply-To: <gHyhP1AZqkBsRi0hv6l8PDU6sBL-xpDdUXlo7Wc7CdcG51IQsX0yIsJttySsSRfLoZZDMpKZALvQ4tCQIMnLEFoWtSyuSB1OOcQor4cIfuQ=@pm.me>
[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]
Hi Seth,
On Wed, Jan 07, 2026 at 02:08:38AM +0000, Seth McDonald wrote:
> On Wednesday, 7 January 2026 at 00:13, Alejandro Colomar <alx@kernel.org> wrote:
> > Hi Seth,
> >
> > On Tue, Jan 06, 2026 at 05:08:01PM +1000, Seth McDonald wrote:
> > > pid_t(3type), uid_t(3type), and gid_t(3type) were initially not
> > > specified as integer types, but as arithmetic types:
> > >
> > > "All of the types listed in Table 2-1 shall be arithmetic types; pid_t
> > > shall be a signed arithmetic type."[1]
> > >
> > > This technically means the types could be floating-point arithmetic
> > > types in systems conforming to early versions of POSIX.1.
> >
> > But did any implementations do this? As far as I know, there were none,
> > which turns this into something that was only true in paper, and can be
> > entirely ignored.
>
> While I'm not the most knowledgeable on past implementations, I too
> can't think of any that used non-integer values for these types. The
> rationale for them doesn't mention floating-point types,[1] which does
> suggest there weren't any such implementations to consider.
>
> The purpose of this patch was mainly to document a quirk in the language
> of early specifications, rather than to imply that such quirky
> implementations exist and should be accounted for. However, if this
> isn't appropriate and no such implementations can be found, then I'd
> agree the paragraph probably shouldn't be added.
I think it would be better to ignore it as a defect in the specification
that didn't get noticed by implementors, and never affected real users.
It would be a waste of manual page real estate.
Have a lovely day!
Alex
> ----
> [1] IEEE Std 1003.1-2024, Volume 4, Appendix B.2.11.1 "Defined Types",
> p. 3838.
> <https://pubs.opengroup.org/onlinepubs/9799919799/xrat/V4_xsh_chap01.html>
>
> ----
> Seth McDonald.
> sethmcmail at pm dot me (mailing lists)
> 2336 E8D2 FEB1 5300 692C 62A9 5839 6AD8 9243 D369
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-07 7:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 7:07 [PATCH v1 00/15] man/man3type/*: Update history of types A-INTN Seth McDonald
2026-01-06 7:07 ` [PATCH v1 01/15] man/man3type/aiocb.3type: HISTORY: Update first POSIX appearance of aiocb(3type) Seth McDonald
2026-01-06 13:56 ` Alejandro Colomar
2026-01-06 7:07 ` [PATCH v1 02/15] man/man3type/blk{cnt,size}_t.3type: HISTORY: Update first SUS appearance of blk{cnt,size}_t(3type) Seth McDonald
2026-01-06 13:57 ` Alejandro Colomar
2026-01-06 7:07 ` [PATCH v1 03/15] man/man3type/cc_t.3type: HISTORY: Update first POSIX appearance of types Seth McDonald
2026-01-06 13:57 ` Alejandro Colomar
2026-01-06 7:07 ` [PATCH v1 04/15] man/man3type/clockid_t.3type: HISTORY: Update first POSIX appearance of clockid_t(3type) Seth McDonald
2026-01-06 13:57 ` Alejandro Colomar
2026-01-06 7:07 ` [PATCH v1 05/15] man/man3type/clock_t.3type: HISTORY: Update first POSIX appearance of clock_t(3type) Seth McDonald
2026-01-06 13:58 ` Alejandro Colomar
2026-01-06 7:07 ` [PATCH v1 06/15] man/man3type/dev_t.3type: HISTORY: Update first POSIX appearance of dev_t(3type) Seth McDonald
2026-01-06 13:58 ` Alejandro Colomar
2026-01-06 7:07 ` [PATCH v1 07/15] man/man3type/div_t.3type: HISTORY: Split [l]div_t(3type) and {ll,imax}div_t(3type) Seth McDonald
2026-01-06 14:03 ` Alejandro Colomar
2026-01-06 7:07 ` [PATCH v1 08/15] man/man3type/div_t.3type: HISTORY: Update first SUS appearance of [l]div_t(3type) Seth McDonald
2026-01-06 7:07 ` [PATCH v1 09/15] man/man3type/FILE.3type: HISTORY: Update first POSIX appearance of FILE(3type) Seth McDonald
2026-01-06 14:06 ` Alejandro Colomar
2026-01-06 7:07 ` [PATCH v1 10/15] man/man3type/id_t.3type: HISTORY: Split id_t(3type) from [pug]id_t(3type) Seth McDonald
2026-01-06 14:07 ` Alejandro Colomar
2026-01-06 7:08 ` [PATCH v1 11/15] man/man3type/id_t.3type: HISTORY: Update first POSIX appearance of [pug]id_t(3type) Seth McDonald
2026-01-06 14:07 ` Alejandro Colomar
2026-01-06 7:08 ` [PATCH v1 12/15] man/man3type/id_t.3type: HISTORY: Mention change in datatypes " Seth McDonald
2026-01-06 14:12 ` Alejandro Colomar
2026-01-07 1:54 ` Collin Funk
2026-01-07 2:08 ` Seth McDonald
2026-01-07 7:55 ` Alejandro Colomar [this message]
2026-01-06 7:08 ` [PATCH v1 13/15] man/man3type/id_t.3type: HISTORY: Update first POSIX appearance of id_t(3type) Seth McDonald
2026-01-06 7:08 ` [PATCH v1 14/15] man/man3type/intN_t.3type: HISTORY: Split types and macros Seth McDonald
2026-01-06 14:16 ` Alejandro Colomar
2026-01-06 7:08 ` [PATCH v1 15/15] man/man3type/intN_t.3type: HISTORY: Update first SUS appearance of [u]intN_t(3type) Seth McDonald
2026-01-06 14:17 ` Alejandro Colomar
2026-01-06 12:34 ` [PATCH v1 00/15] man/man3type/*: Update history of types A-INTN Alejandro Colomar
2026-01-06 14:18 ` Alejandro Colomar
2026-01-07 3:33 ` Seth McDonald
2026-01-07 7:57 ` Alejandro Colomar
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=aV4RGWzP3C9pbjI8@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=sethmcmail@pm.me \
/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