From: Paul Eggert <eggert@cs.ucla.edu>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
gcc-patches@gcc.gnu.org, libc-alpha@sourceware.org,
linux-kernel@vger.kernel.org, jwakely.gcc@gmail.com,
David.Laight@ACULAB.COM
Subject: Re: [PATCH v4 1/2] system_data_types.7: Add 'void *'
Date: Fri, 2 Oct 2020 13:14:01 -0700 [thread overview]
Message-ID: <ff1700df-d383-44e7-24b4-da10000f83fc@cs.ucla.edu> (raw)
In-Reply-To: <d794a058-0506-7c3c-6f3e-518a788933af@gmail.com>
On 10/2/20 11:38 AM, Alejandro Colomar wrote:
> .I void *
>
> renders with a space in between.
That's odd, as "man(7)" says "All of the arguments will be printed next to each
other without intervening spaces". I'd play it safe and quote the arg anyway.
> > %p works with any object pointer type (or in POSIX, any pointer type),
> > not just void *.
> In theory, no (if otherwise, I'd like to know why):
Oh, you're right. I had missed that. In GNU/Linux hosts, though, any pointer
(including function pointers) can be given to %p.
The only platforms where %p wouldn't work on all pointers would be platforms
like IBM i, which has both 64-bit (process local) pointers and 128-bit (tagged
space) pointers and where you can declare and use pointers of different widths
in the same program.
next prev parent reply other threads:[~2020-10-02 20:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 12:16 [PATCH 0/2] Document 'void *' Alejandro Colomar
2020-10-02 12:16 ` [PATCH 1/2] system_data_types.7: Add " Alejandro Colomar
2020-10-02 13:15 ` Jonathan Wakely
2020-10-02 13:26 ` David Laight
2020-10-02 12:16 ` [PATCH 2/2] void.3: New link to system_data_types(7) Alejandro Colomar
2020-10-02 15:14 ` [PATCH v4 0/2] Document 'void *' Alejandro Colomar
2020-10-02 19:28 ` [PATCH v5 " Alejandro Colomar
2020-10-02 19:28 ` [PATCH v5 1/2] system_data_types.7: Add " Alejandro Colomar
2020-10-03 8:01 ` Michael Kerrisk (man-pages)
2020-10-02 19:28 ` [PATCH v5 2/2] void.3: New link to system_data_types(7) Alejandro Colomar
2020-10-03 8:01 ` Michael Kerrisk (man-pages)
2020-10-02 15:14 ` [PATCH v4 1/2] system_data_types.7: Add 'void *' Alejandro Colomar
2020-10-02 16:53 ` Paul Eggert
2020-10-02 18:38 ` Alejandro Colomar
2020-10-02 20:14 ` Paul Eggert [this message]
2020-10-02 20:27 ` Alejandro Colomar
2020-10-03 7:10 ` Michael Kerrisk (man-pages)
2020-10-03 7:48 ` G. Branden Robinson
2020-10-03 8:55 ` Alejandro Colomar
2020-10-03 11:47 ` Alejandro Colomar
2020-10-03 11:52 ` Michael Kerrisk (man-pages)
2020-10-02 15:14 ` [PATCH v4 2/2] void.3: New link to system_data_types(7) 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=ff1700df-d383-44e7-24b4-da10000f83fc@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=David.Laight@ACULAB.COM \
--cc=colomar.6.4.3@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).