public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Seth McDonald <sethmcmail@pm.me>,  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: Tue, 06 Jan 2026 17:54:46 -0800	[thread overview]
Message-ID: <87jyxumbkp.fsf@gmail.com> (raw)
In-Reply-To: <aV0XZSgwGCE5G65j@devuan>

[-- Attachment #1: Type: text/plain, Size: 2340 bytes --]

Alejandro Colomar <alx@kernel.org> writes:

> 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.

I don't think any did. It would surely be an interesting, to put it
nicely, decision if they did.

Here is the 2001 request that was accepted to make this change, for
reference [1]:

 _____________________________________________________________________________

 Problem:

 Currently uid_t and gid_t are only required to be arithmetic types.
 However, there are various commands such as "id" and "ls -nl" that
 are required to output UID and GID values using "%u" format (i.e. as
 unsigned decimal integers).  Now that POSIX.1 and POSIX.2 are being
 merged into a single standard, it would make sense to remove this
 anomaly by requiring uid_t and gid_t to be integer types.  The same
 applies to nlink_t ("ls -l" uses %u).  Also, if uid_t and gid_t are
 changed to integer types then id_t should be as well (since pid_t
 is already).

 I realise it is debatable whether this change is in scope.  I believe
 it is, since it addresses a discrepancy between two base documents.
 In any case, if the change is considered to be out of scope, it can
 easily be brought into scope by filing a POSIX interp request.
 If it is rejected for being out of scope, please give an indication
 of whether it would be accepted if resubmitted after it has been
 brought into scope.

 Action:

 Add the following line after line 13255 :

     * nlink_t, uid_t, gid_t and id_t shall be integer types

 _____________________________________________________________________________

My impression is they probably left it a bit under specified accidentally
before that change.

Collin

[1] https://www.opengroup.org/austin/docs/austin_74.txt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2026-01-07  1:54 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 [this message]
2026-01-07  2:08     ` Seth McDonald
2026-01-07  7:55       ` Alejandro Colomar
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=87jyxumbkp.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=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