public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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 16:43:23 +0200	[thread overview]
Message-ID: <cfd18e0f0807210743p69793dadq616c3e8ecf43d552@mail.gmail.com> (raw)
In-Reply-To: <20080721141514.GB11396@mette>

On Mon, Jul 21, 2008 at 4:15 PM, Andries E. Brouwer
<Andries.Brouwer-rh8NL+sEX9E@public.gmane.org> wrote:
> On Mon, Jul 21, 2008 at 01:36:52PM +0200, Michael Kerrisk wrote:
>> 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?
>
> Yes.
>
> These are different floating point values, and sometimes the
> difference is important. In cases of total loss of precision
> it is the only bit left. At a branch cut one has a discontinuity
> and for example the imaginary part of clog(0.0) will be 0
> while the imaginary part of clog(-0.0) is pi*I.

Thanks Andries.  I will attend to the difference in my updates.

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
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:[~2008-07-21 14:43 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
     [not found]       ` <cfd18e0f0807210436h558aae2cu46f0100c439a8e4a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-21 14:15         ` Andries E. Brouwer
2008-07-21 14:43           ` Michael Kerrisk [this message]
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=cfd18e0f0807210743p69793dadq616c3e8ecf43d552@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