[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5b01a17e-5819-115f-7972-7f849d4356df@gmail.com>
Date: Fri, 2 Oct 2020 22:27:20 +0200
From: Alejandro Colomar <colomar.6.4.3@...il.com>
To: Paul Eggert <eggert@...ucla.edu>, mtk.manpages@...il.com,
"G. Branden Robinson" <g.branden.robinson@...il.com>
Cc: linux-man@...r.kernel.org, gcc-patches@....gnu.org,
libc-alpha@...rceware.org, linux-kernel@...r.kernel.org,
jwakely.gcc@...il.com, David.Laight@...LAB.COM
Subject: Re: [PATCH v4 1/2] system_data_types.7: Add 'void *'
Hi Paul,
On 2020-10-02 22:14, Paul Eggert wrote:
> 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.
Oops, that's a bug in man(7).
Don't worry about it.
Michael, you might want to have a look at it.
I'll also add Branden, who might have something to say about it.
>
>> > %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.
:-)
Cheers,
Alex
Powered by blists - more mailing lists