From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>,
GNU C Library <libc-alpha@sourceware.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [PATCH 0/2] Document void *
Date: Sat, 3 Oct 2020 13:44:11 +0200 [thread overview]
Message-ID: <1363a952-79d5-e41e-652c-14c67ac47a7b@gmail.com> (raw)
In-Reply-To: <CAH6eHdQhh46TjVc72meWFTWCi7iouAod0iC1zLRga+c-36G+ig@mail.gmail.com>
Hi Jonathan!
On 10/2/20 3:19 PM, Jonathan Wakely wrote:
> On Thu, 1 Oct 2020 at 16:51, Alejandro Colomar via Gcc <gcc@gcc.gnu.org> wrote:
>>
>> Hi Michael,
>>
>> On 2020-10-01 17:34, Michael Kerrisk (man-pages) wrote:
>>> Hello Alex,
>>>
>>> On 10/1/20 5:06 PM, Alejandro Colomar wrote:
>>>> Hello Michael,
>>>>
>>>> This type is very special,
>>>> so I will probably have missed some details about it.
>>>
>>> I do wonder if we actually need this in page at all, and given:
>>
>>
>> I think it should be.
>> I would also document 'void', even if it's a bit weird...
>> They are very useful, so why not document them?
>
> Because the man-pages are not a tutorial for the C language.
>
> "The Linux man-pages project documents the Linux kernel and C library
> interfaces that are employed by user-space programs."
>
> void and void* are not APIs.
Agreed, but the rationale of the page is to document topics
that are helpful when using the APIs. And, as I noted already
stuff like 'void *' is borerline, but I think it's helpful
to have some info summarized in one place. And, additionally,
POSIX adds a detail to the C standard (casting between
void * and function pointer).
By the way, thanks for all of your input so far. Among
other things, it made me realize that some navigational
corrections were needed.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-10-03 11:44 UTC|newest]
Thread overview: 33+ 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
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) [this message]
2020-10-02 12:16 [PATCH 0/2] Document 'void *' 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=1363a952-79d5-e41e-652c-14c67ac47a7b@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
/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).