From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: mpz_cmp_d and NaNs in = and <
Date: 17 May 2003 13:19:38 +0200 [thread overview]
Message-ID: <87wugp7rcl.fsf@zagadka.ping.de> (raw)
In-Reply-To: <874r3unzq1.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> rm@fabula.de writes:
> >
> > Divide by it and you'll see :-)
>
> Oh, well, all I mean is that it's hard to see what it could represent.
> A sort of remnant parity indicating how many positives and negatives
> went into a product or something. But I don't pretend to any great
> expertise in this sort of area, so maybe it's good for something.
There ought to be some good stuff in
Branch Cuts for Complex Elementary Functions,
or Much Ado About Nothing's Sign Bit
in The State of the Art in Numerical Analysis,
(eds. Iserles and Powell), Clarendon Press, Oxford, 1987.
but I couldn't find an online copy.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-05-17 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 23:24 mpz_cmp_d and NaNs in = and < Kevin Ryde
2003-05-09 23:16 ` Kevin Ryde
2003-05-10 12:52 ` Marius Vollmer
2003-05-12 23:13 ` Kevin Ryde
2003-05-13 10:21 ` rm
2003-05-17 1:12 ` Kevin Ryde
2003-05-17 11:19 ` Marius Vollmer [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wugp7rcl.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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).