From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org,
Alejandro Colomar <colomar.6.4.3@gmail.com>
Subject: [PATCH v2 04/10] system_data_types.7: Add float_t
Date: Fri, 25 Sep 2020 13:19:23 +0200 [thread overview]
Message-ID: <20200925111922.222149-1-colomar.6.4.3@gmail.com> (raw)
In-Reply-To: <94936b66-4d20-1168-546f-64ac63018845@gmail.com>
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
Hi Michael,
On 2020-09-25 11:30, Michael Kerrisk (man-pages) wrote:
>> I removed the "intended" part to simplify it a bit. Do you prefer to
>> keep it?
> Well, as long as you are going to lift the detail about "most
> efficient" from the C standard, I'd be inclined to keep
> the word "intended" from the standard as well. But I do not feel
> strongly about it.
>
Fair enough.
On 2020-09-25 11:30, Michael Kerrisk (man-pages) wrote:
>> BTW, I'll also add a note that FLT_EVAL_METHOD is defined in <float.h>
>> Would you add that to "Notes", or as part of the description?
> As part of the description I think. (And I don't mind if it's
> repeated in the double_t description.)
I think there was a misunderstanding; maybe I should have been clearer:
I meant to write about <float.h> in the "Notes" of the type,
and not in the "NOTES" of the entire page.
However, I decided to do it in the description of the type as you said,
because it was a bit simpler.
The other version would have resulted in this code, just for you to see:
[[
.TP
.I double_t
.RS
.PP
Include:
.IR <math.h> .
.PP
The implementation's most efficient floating type at least as wide as
.IR double .
Its type depends on the value of the macro
.BR FLT_EVAL_METHOD :
.TP
0
.I double_t
is
.IR double .
.TP
1
.I double_t
is
.IR double .
.TP
2
.I double_t
is
.IR "long double" .
.IP
For other values of
.BR FLT_EVAL_METHOD ,
the type of
.I double_t
is implementation-defined.
.PP
Conforming to: C99 and later; POSIX.1-2001 and later.
.PP
Notes: The macro
.B FLT_EVAL_METHOD
is defined in
.IR <float.h> .
.PP
See also the
.I float_t
type in this page.
.RE
]]
Cheers,
Alex
man7/system_data_types.7 | 42 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
index b04457bbf..aa5ab95e9 100644
--- a/man7/system_data_types.7
+++ b/man7/system_data_types.7
@@ -147,6 +147,48 @@ Conforming to: C99 and later; POSIX.1-2001 and later.
.IP
See also:
.BR fenv (3)
+.\"------------------------------------- float_t ----------------------/
+.TP
+.I float_t
+.IP
+Include:
+.IR <math.h> .
+.IP
+The implementation's most efficient floating type at least as wide as
+.IR float .
+Its type depends on the value of the macro
+.BR FLT_EVAL_METHOD ,
+defined in
+.IR <float.h> :
+.RS
+.TP
+0
+.I float_t
+is
+.IR float .
+.TP
+1
+.I float_t
+is
+.IR double .
+.TP
+2
+.I float_t
+is
+.IR "long double" .
+.IP
+For other values of
+.BR FLT_EVAL_METHOD ,
+the type of
+.I float_t
+is implementation-defined.
+.RE
+.IP
+Conforming to: C99 and later; POSIX.1-2001 and later.
+.IP
+See also the
+.I double_t
+type in this page.
.\"------------------------------------- gid_t ------------------------/
.TP
.I gid_t
--
2.28.0
next prev parent reply other threads:[~2020-09-25 11:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 7:31 [PATCH 00/10] Add types, and some fixes Alejandro Colomar
2020-09-25 7:31 ` [PATCH 01/10] system_data_types.7: ffix Alejandro Colomar
2020-09-25 7:57 ` Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 02/10] system_data_types.7: Add lconv Alejandro Colomar
2020-09-25 7:59 ` Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 03/10] lconv.3: New link to system_data_types(7) Alejandro Colomar
2020-09-25 8:00 ` Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 04/10] system_data_types.7: Add float_t Alejandro Colomar
2020-09-25 8:13 ` Michael Kerrisk (man-pages)
2020-09-25 8:22 ` Alejandro Colomar
2020-09-25 9:30 ` Michael Kerrisk (man-pages)
2020-09-25 11:19 ` Alejandro Colomar [this message]
2020-09-25 12:01 ` [PATCH v2 " Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 05/10] float_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-25 12:01 ` Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 06/10] system_data_types.7: Add double_t Alejandro Colomar
2020-09-25 11:22 ` [PATCH v2 " Alejandro Colomar
2020-09-25 12:01 ` [PATCH " Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 07/10] double_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-25 12:01 ` Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 08/10] seccomp.2: Remove unneeded cast Alejandro Colomar
2020-09-25 8:34 ` Michael Kerrisk (man-pages)
2020-09-25 8:42 ` Alejandro Colomar
2020-09-25 9:23 ` Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 09/10] seccomp.2: Use ARRAY_SIZE() macro instead of raw sizeof division Alejandro Colomar
2020-09-25 9:25 ` Michael Kerrisk (man-pages)
2020-09-25 7:31 ` [PATCH 10/10] getgrent_r.3: Declare variables with different types in different lines Alejandro Colomar
2020-09-25 7:57 ` 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=20200925111922.222149-1-colomar.6.4.3@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).