From: Florian Weimer <fweimer@redhat.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org>,
mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] system_data_types.7: Document size_t
Date: Fri, 18 Sep 2020 19:27:21 +0200 [thread overview]
Message-ID: <87v9gb0zd2.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <3d88ecab-1c36-9081-4195-4e1fd054fadf@gmail.com> (Alejandro Colomar's message of "Fri, 18 Sep 2020 17:53:15 +0200")
* Alejandro Colomar:
> I think I prefer to leave it opaque, showing only the requirements
> that POSIX and C make.
>
> There's really not much gain (basically uint and ulong cover most of the
> possibilities; and still it's not a guarantee).
> And readers might write non-portable code because of reading that.
My idea was it that it stresses that you have to use %zu in order to be
portable. %lu works almost everywhere, so that's any easy mistake to
make because it still leads to -Werror build failures on s390 (31-bit).
Likewise for %ld for ptrdiff_t, it should be %td.
> On 2020-09-18 16:34, Florian Weimer wrote:
>> that the length modifier for printf and scanf is z, commently used as
>> %zu or %zx (%zd is for ssize_t).
>
> Good idea.
>
> Would you prefer that, or just refer to printf(3) in See also?.
I think it makes sense to spell out %zu and %zx explicitly.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-09-18 17:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 11:27 [PATCH 0/2] Document size_t Alejandro Colomar
2020-09-18 11:27 ` [PATCH 1/2] system_data_types.7: " Alejandro Colomar
2020-09-18 14:34 ` Florian Weimer
2020-09-18 15:53 ` Alejandro Colomar
2020-09-18 17:27 ` Florian Weimer [this message]
2020-09-18 17:42 ` Paul Eggert
2020-09-18 17:53 ` Florian Weimer
2020-09-30 15:50 ` Joseph Myers
2020-09-18 20:13 ` Michael Kerrisk (man-pages)
2020-09-28 13:41 ` Dave Martin
2020-09-28 13:48 ` Alejandro Colomar
2020-09-28 13:55 ` G. Branden Robinson
2020-09-28 14:15 ` Dave Martin
2020-09-28 14:51 ` Alejandro Colomar
2020-09-28 15:16 ` [RFC] system_data_types.7: wfix + ffix Alejandro Colomar
2020-09-29 10:37 ` Dave Martin
2020-09-29 11:34 ` Michael Kerrisk (man-pages)
2020-09-29 12:10 ` Alejandro Colomar
2020-09-29 14:22 ` [PATCH v2] system_data_types.7: Improve "Include" wording and format, and explain it in NOTES Alejandro Colomar
2020-09-29 14:43 ` Dave Martin
2020-09-29 14:52 ` Alejandro Colomar
2020-09-29 15:06 ` Michael Kerrisk (man-pages)
2020-09-29 15:13 ` Dave Martin
2020-09-29 15:21 ` Alejandro Colomar
2020-09-29 15:10 ` Dave Martin
2020-09-29 11:57 ` [RFC] system_data_types.7: wfix + ffix Alejandro Colomar
2020-09-30 17:16 ` [PATCH 1/2] system_data_types.7: Document size_t Joseph Myers
2020-09-29 11:11 ` Michael Kerrisk (man-pages)
2020-09-28 14:47 ` Alejandro Colomar
2020-09-18 11:27 ` [PATCH 2/2] size_t.3: New link to new documented type in system_data_types(7) Alejandro Colomar
2020-09-18 20:14 ` Michael Kerrisk (man-pages)
2020-09-18 20:13 ` [PATCH 0/2] Document size_t Michael Kerrisk (man-pages)
2020-09-18 21:28 ` Alejandro Colomar
2020-09-18 21:32 ` Florian Weimer
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=87v9gb0zd2.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=colomar.6.4.3@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.