From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: Paul Eggert <eggert@cs.ucla.edu>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org,
gcc@gcc.gnu.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] system_data_types.7: Add 'void *'
Date: Fri, 2 Oct 2020 10:48:58 +0200 [thread overview]
Message-ID: <7c55f6cf-8cb1-7b63-30ec-990f8c370bf5@gmail.com> (raw)
In-Reply-To: <4b86f6e9-0d8a-f14a-73ce-ebbdc9d9edba@gmail.com>
Hi Michael,
On 2020-10-02 10:24, Alejandro Colomar wrote:
> On 2020-10-01 19:32, Paul Eggert wrote:
> > For 'void *' you should also mention that one cannot use arithmetic on
> > void * pointers, so they're special in that way too.
>
> Good suggestion!
>
> > Also, you should
> > warn that because one can convert from any pointer type to void * and
> > then to any other pointer type, it's a deliberate hole in C's
> > type-checking.
>
> Also good. I'll talk about generic function parameters for this.
I think the patch as is now is complete enough to be added.
So I won't rewrite it for now.
Please review the patch as is,
and I'll add more info to this type in the future.
Thanks,
Alex
next prev parent reply other threads:[~2020-10-02 8:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 15:06 [PATCH 0/2] Document void * Alejandro Colomar
2020-10-01 15:06 ` [PATCH 1/2] system_data_types.7: Add 'void *' Alejandro Colomar
2020-10-01 15:06 ` [PATCH 2/2] void-*.3: New link to system_data_types(7) Alejandro Colomar
2020-10-01 15:34 ` [PATCH 0/2] Document void * Michael Kerrisk (man-pages)
2020-10-01 15:40 ` Alejandro Colomar
2020-10-01 15:49 ` [PATCH v2 0/2] Document 'void *' Alejandro Colomar
2020-10-01 15:49 ` [PATCH v2 1/2] system_data_types.7: Add " Alejandro Colomar
2020-10-01 16:38 ` Michael Kerrisk (man-pages)
2020-10-01 16:55 ` Alejandro Colomar
2020-10-02 11:54 ` Michael Kerrisk (man-pages)
2020-10-08 13:52 ` Vincent Lefevre
2020-10-12 9:36 ` Michael Kerrisk (man-pages)
2020-10-01 17:32 ` Paul Eggert
2020-10-02 8:24 ` Alejandro Colomar
2020-10-02 8:48 ` Alejandro Colomar [this message]
2020-10-02 11:44 ` Michael Kerrisk (man-pages)
2020-10-02 9:10 ` David Laight
2020-10-02 17:00 ` Paul Eggert
2020-10-02 10:49 ` Jonathan Wakely
2020-10-02 11:31 ` Michael Kerrisk (man-pages)
2020-10-02 13:06 ` Jonathan Wakely
2020-10-02 13:20 ` Alejandro Colomar
2020-10-02 13:27 ` Jonathan Wakely
2020-10-02 13:51 ` Alejandro Colomar
2020-10-03 8:00 ` Navigational corrections (was: Re: [PATCH v2 1/2] system_data_types.7: Add 'void *') Michael Kerrisk (man-pages)
2020-10-03 9:16 ` Navigational corrections Alejandro Colomar
2020-10-03 11:39 ` Michael Kerrisk (man-pages)
2020-10-05 22:08 ` Alejandro Colomar
2020-10-07 6:53 ` Michael Kerrisk (man-pages)
2020-10-01 15:49 ` [PATCH v2 2/2] void.3: New link to system_data_types(7) Alejandro Colomar
2020-10-02 13:19 ` [PATCH 0/2] Document void * Jonathan Wakely
2020-10-03 11:44 ` 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=7c55f6cf-8cb1-7b63-30ec-990f8c370bf5@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=gcc@gcc.gnu.org \
--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).