Hi Alex, A few comments here that also apply for the double_t patch. Could you revise please? On 9/25/20 9:31 AM, Alejandro Colomar wrote: > Signed-off-by: Alejandro Colomar <colomar.6.4.3@xxxxxxxxx> > --- > man7/system_data_types.7 | 36 ++++++++++++++++++++++++++++++++++++ > 1 file changed, 36 insertions(+) > > diff --git a/man7/system_data_types.7 b/man7/system_data_types.7 > index b04457bbf..238b9593b 100644 > --- a/man7/system_data_types.7 > +++ b/man7/system_data_types.7 > @@ -147,6 +147,42 @@ 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 . The C standard is rather terse here. Perhaps we could make the reader's life a little easier. How about something like: [[ This a type that is intended to be the implementation's most efficient floating type that is at least as wide as .IR float . ]] > +Its type depends on the value of the macro > +.BR FLT_EVAL_METHOD : > +.RS > +.IP * > +0; > +.I float_t > +is > +.IR float . > +.IP * > +1; > +.I float_t > +is > +.IR double . > +.IP * > +2; > +.I float_t > +is > +.IR "long double" . > +.IP * > +Other implementation-defined values. > +.RE I think we can format this better as a hanging list. Something like this: [[ .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. ]] > +.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 Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
