From: "Michael Kerrisk" <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: "Andries E. Brouwer" <Andries.Brouwer-rh8NL+sEX9E@public.gmane.org>
Cc: aj-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Fabian Kreutz
<kreutz-WMH0Fc3rTAP1qYPpFx2fzhvVK+yQ3ZXh@public.gmane.org>
Subject: Re: math_error.7 draft 3, for review
Date: Mon, 21 Jul 2008 13:36:52 +0200 [thread overview]
Message-ID: <cfd18e0f0807210436h558aae2cu46f0100c439a8e4a@mail.gmail.com> (raw)
In-Reply-To: <20080716213732.GA10011@ub>
Hi Andries,
Reading the POSIX.1 specs of various functions, I see that sometimes
they talk of the return value of a function as being +0, sometimes
+-0, and sometimes -0. Does one need to care about this? (e.g., in
updating them man-pages, I'm inclined to group the 0 cases togetehr,
where possible). If one does need to care, then could you explain to
me why? Are there cases where one gets bitten by not caring? (I've
had a browse through the C standard, but I'm not sure that I am yet
any the wiser.)
Hmmm -- just now, I find the Wikipedia article:
http://en.wikipedia.org/wiki/%E2%88%920_(number). So, are these the
only cases that matter (quoting test from wp):
* using the copysign() function, which is defined by IEEE 754 to copy
the sign of the zero, to some non-zero number
* dividing the number into a positive number—the resulting Infinity
will reflect the sign of the zero.
?
It starts to sound like I should care about postive and negative zero
when rewriting the man pages, or?
Cheers,
Michael
--
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
next prev parent reply other threads:[~2008-07-21 11:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 13:47 math_error.7 draft 3, for review Michael Kerrisk
[not found] ` <cfd18e0f0807160647o776d8523yb2f1ed4f0d946911-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-16 21:37 ` Andries E. Brouwer
2008-07-21 11:36 ` Michael Kerrisk [this message]
[not found] ` <cfd18e0f0807210436h558aae2cu46f0100c439a8e4a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-21 14:15 ` Andries E. Brouwer
2008-07-21 14:43 ` Michael Kerrisk
2008-07-21 10:12 ` Michael Kerrisk
[not found] ` <cfd18e0f0807210312s78b1183ao5ec2932a5317decc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-25 9:31 ` Andreas Jaeger
[not found] ` <cfd18e0f0807210314s6556f15bue41b1af46e28f77d@mail.gmail.com>
[not found] ` <517f3f820807210326x30ce95dayf18d72ba0ce03588@mail.gmail.com>
[not found] ` <m3r69ib8sz.fsf@gromit.moeb>
[not found] ` <m3r69ib8sz.fsf-Qr39nsLl7G5WFLYQ/5USTw@public.gmane.org>
2008-07-25 9:51 ` Michael Kerrisk
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=cfd18e0f0807210436h558aae2cu46f0100c439a8e4a@mail.gmail.com \
--to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=Andries.Brouwer-rh8NL+sEX9E@public.gmane.org \
--cc=aj-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
--cc=kreutz-WMH0Fc3rTAP1qYPpFx2fzhvVK+yQ3ZXh@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox