From: Paul Eggert <eggert@cs.ucla.edu>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>, mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org, gcc@gcc.gnu.org
Subject: Re: [PATCH v2 1/4] system_data_types.7: Add int_leastN_t family of types
Date: Thu, 1 Oct 2020 10:38:22 -0700 [thread overview]
Message-ID: <b116e906-2a5d-1a7e-2969-52036ab3e8c3@cs.ucla.edu> (raw)
In-Reply-To: <20201001143535.98990-2-colomar.6.4.3@gmail.com>
On 10/1/20 7:35 AM, Alejandro Colomar via Libc-alpha wrote:
> +The narrowest signed integer type
> +of a width of at least N bits,
Motivation is missing here. Why is there an int_leastN_t type at all? Also, on
all glibc platforms, int_leastN_t is equivalent to intN_t; this should probably
be mentioned.
Similarly for int_fastN_t.
next prev parent reply other threads:[~2020-10-01 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 14:35 [PATCH v2 0/4] Document [u]int_leastN_t Alejandro Colomar
2020-10-01 14:35 ` [PATCH v2 1/4] system_data_types.7: Add int_leastN_t family of types Alejandro Colomar
2020-10-01 17:38 ` Paul Eggert [this message]
2020-10-02 8:35 ` Alejandro Colomar
2020-10-02 13:09 ` Jonathan Wakely
2020-10-01 14:35 ` [PATCH v2 2/4] int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3, int_leastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 15:26 ` Michael Kerrisk (man-pages)
2020-10-01 14:35 ` [PATCH v2 3/4] system_data_types.7: Add uint_leastN_t family of types Alejandro Colomar
2020-10-01 15:26 ` Michael Kerrisk (man-pages)
2020-10-01 14:35 ` [PATCH v2 4/4] uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3, uint_leastN_t.3: New links to system_data_types(7) Alejandro Colomar
2020-10-01 15:26 ` Michael Kerrisk (man-pages)
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=b116e906-2a5d-1a7e-2969-52036ab3e8c3@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=colomar.6.4.3@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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).