From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: min, max and nans
Date: 19 Jun 2003 01:36:47 +0200 [thread overview]
Message-ID: <8765n30xgw.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87d6hgw5wh.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> I notice C99 fmin and fmax return the other operand when one is a NaN,
> and return NaN only when both are NaNs.
>
> I tend to think of nan as indicating something evil, and it should be
> propagated. But the c99 way would be a possibility to consider.
Yep. Does the IEEE standard say aomething about max and min?
--
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-06-18 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 23:26 min, max and nans Kevin Ryde
2003-05-17 20:02 ` Marius Vollmer
2003-05-30 0:20 ` Kevin Ryde
2003-06-04 16:08 ` Kevin Ryde
2003-06-05 12:48 ` Marius Vollmer
2003-06-06 16:03 ` Mikael Djurfeldt
2003-06-06 23:17 ` Marius Vollmer
2003-06-15 0:17 ` Kevin Ryde
2003-06-18 23:36 ` 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=8765n30xgw.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).