From: Joseph Myers <joseph@codesourcery.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: libc-alpha@sourceware.org, "Rich Felker" <dalias@libc.org>,
"Stefan Puiu" <stefan.puiu@gmail.com>,
"Michael Kerrisk" <mtk.manpages@gmail.com>,
наб <nabijaczleweli@nabijaczleweli.xyz>,
"Jakub Wilk" <jwilk@jwilk.net>
Subject: Re: [RFC v2 1/2] sys/types.h: Define new type: snseconds_t
Date: Tue, 7 Dec 2021 23:56:28 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2112072354250.444190@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20211207214814.18553-1-alx.manpages@gmail.com>
On Tue, 7 Dec 2021, Alejandro Colomar via Libc-alpha wrote:
> For this RFC I used snseconds_t for simplicity writing the patch,
> and it helps reviewing it too I think,
> but it can easily be changed later at once.
>
> I'd like some feedback on naming the type nsec_t vs snseconds_t.
My suggestion would be to do things *without* having such a user-visible
name at all, just the __*_t name (which arguably makes sense as an
internal cleanup anyway, given that we need to handle the peculiarities of
the x32 kernel ABI). The choice of user-visible name, if any, could be
considered separately and in conjunction with WG14 / WG21 / Austin Group
consideration of the issue.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-12-07 23:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 11:19 [PATCH] sys/types.h: Define new types: [s]nseconds_t Alejandro Colomar
2021-12-07 12:36 ` Andreas Schwab
2021-12-07 13:17 ` наб
2021-12-07 18:20 ` Alejandro Colomar (man-pages)
2021-12-07 21:48 ` наб
2021-12-07 19:10 ` Joseph Myers
2021-12-07 15:50 ` Zack Weinberg
2021-12-07 18:24 ` Alejandro Colomar (man-pages)
2021-12-07 21:48 ` [RFC v2 1/2] sys/types.h: Define new type: snseconds_t Alejandro Colomar
2021-12-07 23:56 ` Joseph Myers [this message]
2021-12-08 0:17 ` Paul Eggert
2021-12-08 0:29 ` Rich Felker
2021-12-08 2:26 ` Zack Weinberg
2021-12-08 3:05 ` Rich Felker
2021-12-08 14:34 ` Zack Weinberg
2021-12-08 17:38 ` Rich Felker
2021-12-08 19:52 ` Zack Weinberg
2021-12-08 18:15 ` Adhemerval Zanella
2021-12-08 21:41 ` Joseph Myers
2021-12-07 22:05 ` [RFC v2 2/2] sys/types.h: struct timespec: Use snseconds_t for tv_nsec Alejandro Colomar
2021-12-08 14:47 ` [RFC v3 1/3] bits/types[izes].h: Define new internal type: __snseconds_t Alejandro Colomar
2021-12-08 14:47 ` [RFC v3 2/3] sys/types.h: struct timespec: Use __snseconds_t for tv_nsec Alejandro Colomar
2021-12-08 14:53 ` Zack Weinberg
2021-12-08 15:17 ` Alejandro Colomar (man-pages)
2021-12-08 15:24 ` Joseph Myers
2021-12-08 15:47 ` Alejandro Colomar (man-pages)
2021-12-08 15:59 ` Zack Weinberg
2021-12-08 17:44 ` Rich Felker
2021-12-08 14:48 ` [RFC v3 3/3] sys/types.h: Make snseconds_t user visible Alejandro Colomar
2021-12-08 14:55 ` Zack Weinberg
2021-12-08 15:15 ` Alejandro Colomar (man-pages)
2021-12-08 18:12 ` Paul Eggert
2021-12-08 18:25 ` Rich Felker
2021-12-08 20:10 ` Zack Weinberg
2021-12-08 20:34 ` Rich Felker
2021-12-08 21:12 ` Adhemerval Zanella
2021-12-08 21:53 ` Alejandro Colomar (man-pages)
2021-12-09 19:20 ` Adhemerval Zanella
2021-12-09 19:42 ` Paul Eggert
2021-12-09 19:52 ` Adhemerval Zanella
2021-12-09 20:13 ` Joseph Myers
2021-12-09 20:17 ` Rich Felker
2021-12-09 20:23 ` Alejandro Colomar (man-pages)
2021-12-09 20:29 ` Joseph Myers
2021-12-09 20:34 ` Alejandro Colomar (man-pages)
2021-12-09 20:40 ` Joseph Myers
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=alpine.DEB.2.22.394.2112072354250.444190@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=alx.manpages@gmail.com \
--cc=dalias@libc.org \
--cc=jwilk@jwilk.net \
--cc=libc-alpha@sourceware.org \
--cc=mtk.manpages@gmail.com \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=stefan.puiu@gmail.com \
/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).