From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: ptrace.2: Simplify signature? s/enum \w*/int/
Date: Mon, 8 Feb 2021 23:36:08 +0100 [thread overview]
Message-ID: <bba760a2-b291-d676-2949-90b47f13d4f9@gmail.com> (raw)
In-Reply-To: <e7685576-db7b-f53d-26b9-64ee6621aea1@gmail.com>
[CC += linux-man@]
I forgot the list.
On 2/8/21 11:34 PM, Alejandro Colomar (man-pages) wrote:
> Hi Michael,
>
> I think we should simplify the prototype of ptrace(2) from using 'enum
> __ptrace_request' to 'int'. It is an implementation detail that should
> be transparent to the user. Other pages where glibc uses an 'enum' are
> documented to use 'int' (I don't remember the names of those, but
> remember having seen them a few days ago. Otherwise, we might have to
> document 'enum' elsewhere, which I don't think adds any value. What do
> you think about it?
>
> Thanks,
>
> Alex
>
> -- Alejandro Colomar Linux man-pages comaintainer;
> https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next parent reply other threads:[~2021-02-08 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e7685576-db7b-f53d-26b9-64ee6621aea1@gmail.com>
2021-02-08 22:36 ` Alejandro Colomar (man-pages) [this message]
2021-02-09 18:25 ` ptrace.2: Simplify signature? s/enum \w*/int/ Michael Kerrisk (man-pages)
2021-02-09 22:34 ` Alejandro Colomar (man-pages)
2021-02-10 10:18 ` Alejandro Colomar (man-pages)
2021-02-10 10:20 ` Alejandro Colomar (man-pages)
2021-02-10 21:31 ` Michael Kerrisk (man-pages)
[not found] ` <CAHBesv0hwHLJMzqBq+e4LpDAWV98H4+d5mv4gSbFFWs8oV7b3w@mail.gmail.com>
[not found] ` <20d93fb1-766e-ddf8-a7d8-b00f7bd04cc6@gmail.com>
2021-02-11 17:28 ` Alejandro Colomar (man-pages)
2021-02-13 10:16 ` Alejandro Colomar (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=bba760a2-b291-d676-2949-90b47f13d4f9@gmail.com \
--to=alx.manpages@gmail.com \
--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