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 22:37:54 +0200 [thread overview]
Message-ID: <f3f2d286-a3e6-d399-8ee8-16fa6f000539@gmail.com> (raw)
In-Reply-To: <a8fcbafb-34a1-aeea-eea7-e9202d8f8426@gmail.com>
On 9/22/20 10:32 PM, Alejandro Colomar wrote:
> Actually, POSIX already ripped (part of) the description from the C
> standard:
>
> > Represents the floating-point status flags collectively,
> > including any status the implementation associates with the flags.
>
> This part is in the C standard (and POSIX also has it).
I think they probably have an agreement for this :-).
> > 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.
> > A floating-point control mode is a system variable whose
> > value may be set by the user to affect
> > the subsequent behavior of floating-point arithmetic.
>
> And this is from POSIX only.
>
> How would you go about it?
Just quote POSIX (no need to mention the C standard
when quoting, I think).
> > Represents the floating-point status flags collectively,
> > including any status the implementation associates with the flags.
> POSIX describes a
> > [s/A//] floating-point status flag [s/is/as] 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.
> According to POSIX,
> > [s/A/a/] floating-point control mode is a system variable whose
> > value may be set by the user to affect
> > the subsequent behavior of floating-point arithmetic.
I think so.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-09-22 20:38 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 ` [PATCH 1/2] system_data_types.7: Add 'fexcept_t' Michael Kerrisk (man-pages)
2020-09-22 20:05 ` 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) [this message]
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=f3f2d286-a3e6-d399-8ee8-16fa6f000539@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;
as well as URLs for NNTP newsgroup(s).