All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Grant <jg-hus3n9K41k0@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: modf, modff, modfl etc
Date: Mon, 7 Oct 2013 19:04:57 +0100	[thread overview]
Message-ID: <CAGc9Evdt87nafwpixnSt9TiZx27Z1sfONEkTvhgmue9DzDFSbw@mail.gmail.com> (raw)

Hello mtk

Should functions like modf(), which have float, and long-double
precision include that explanation in the DESCRIPTION section of the
man page? eg. add something about modff, modfl

http://man7.org/linux/man-pages/man3/modf.3.html

Current text:

"The modf() function breaks the argument x into an integral part and a
fractional part, each of which has the same sign as x.  The integral
part is stored in the location pointed to by iptr."


Could be changed to:
"The modf() function breaks the argument x into an integral part and a
fractional part, each of which has the same sign as x.  The integral
part is stored in the location pointed to by iptr. The modff() function
operates the same way with float. The modfl() function operates the
same way with long double"




Similarly same query applies to others:
http://man7.org/linux/man-pages/man3/ldexp.3.html
http://man7.org/linux/man-pages/man3/frexp.3.html


"CONFORMING TO         top

       C99, POSIX.1-2001.  The variant returning double also conforms to
       SVr4, 4.3BSD, C89."

^ Should this say "modf which returns double also conforms to" etc,
just to be clear which one it is?
Does this meant hat modff and modfl don't conform?


Best regards, Jon
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

                 reply	other threads:[~2013-10-07 18:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAGc9Evdt87nafwpixnSt9TiZx27Z1sfONEkTvhgmue9DzDFSbw@mail.gmail.com \
    --to=jg-hus3n9k41k0@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.