From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] system_data_types.7: Add 'fexcept_t'
Date: Tue, 22 Sep 2020 21:57:20 +0200 [thread overview]
Message-ID: <42f8c77e-27a5-651c-9768-fa08d11e5ba2@gmail.com> (raw)
In-Reply-To: <20200922153822.33728-1-colomar.6.4.3@gmail.com>
Hi Alex,
On 9/22/20 5:38 PM, Alejandro Colomar wrote:
> Note: I used this commit to fix the comment that separates with gid_t.
>
> It wasn't aligned with the rest (col 72).
That's fine.
>
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
>
> Hi Michael,
>
> Would you prefer a separate patch for the cosmetic change?
> I put it in the same one, as it was in an adjacent line,
> and the diff looks good; to avoid noise in the log.
> But maybe a separate commit is better.
(It's fine as is.)
>
> Thanks,
>
> Alex
>
> man7/system_data_types.7 | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
> index 59c64fb89..97411a193 100644
> --- a/man7/system_data_types.7
> +++ b/man7/system_data_types.7
> @@ -111,7 +111,29 @@ Conforming to: C99 and later; POSIX.1-2001 and later.
> .IP
> See also:
> .BR fenv (3)
> -.\"------------------------------------- gid_t ----------------------/
> +.\"------------------------------------- fexcept_t --------------------/
> +.TP
> +.I fexcept_t
> +.IP
> +Include:
> +.IR <fenv.h> .
> +.IP
> +Represents the floating-point status flags collectively,
> +including any status the implementation associates with the flags.
> +A floating-point status flag is a system variable
> +whose value is set (but never cleared)
> +when a floating-point exception is raised,
> +which occurs as a side-effect of
> +exceptional floating-point arithmetic to provide auxiliary information.
The previous sentence is rather hard to parse. What (other) part of
the sentence does "to provide auxiliary information" relate to.
I suggest splitting the sentence in two and rewording.
> +A floating-point control mode is a system variable whose
You suddenly introduce "floating-point control mode" here.
How does it relate to the preceding sentences? It's not clear.
Going off to look at the standard... I see that actually your
sentences come pretty much straight from the standard. So, first, I
think the standard could have been clearer here. Second, and more
important, (for copyright reasons) we are on shaky ground if we just
lift whole passages from the standard. The text does really need to
be in your own words. Can you come up with something?
Alternatively, I guess we could explicitly quote the standard.
Something like
POSIX describes this type as follows:
.RS
.PP
[The text]
.RE
> +value may be set by the user to affect
> +the subsequent behavior of floating-point arithmetic.
> +.IP
> +Conforming to: C99 and later; POSIX.1-2001 and later.
> +.IP
> +See also:
> +.BR fenv (3)
> +.\"------------------------------------- gid_t ------------------------/
> .TP
> .I gid_t
> .IP
>
Thanks,
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-09-22 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 15:38 [PATCH 1/2] system_data_types.7: Add 'fexcept_t' Alejandro Colomar
2020-09-22 15:38 ` [PATCH 2/2] fexcept_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-23 13:17 ` [PATCH v2 1/2] system_data_types.7: Add 'fexcept_t' Alejandro Colomar
2020-09-23 13:31 ` Michael Kerrisk (man-pages)
2020-09-23 13:17 ` [PATCH v2 2/2] fexcept_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-23 13:31 ` Michael Kerrisk (man-pages)
2020-09-22 19:57 ` Michael Kerrisk (man-pages) [this message]
2020-09-22 20:05 ` [PATCH 1/2] system_data_types.7: Add 'fexcept_t' Alejandro Colomar
2020-09-22 20:14 ` Michael Kerrisk (man-pages)
2020-09-22 20:32 ` Alejandro Colomar
2020-09-22 20:37 ` 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=42f8c77e-27a5-651c-9768-fa08d11e5ba2@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--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