From: "Yaron Minsky" <yminsky@cs.cornell.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Weird behavior with nan's and min/max
Date: Tue, 14 Oct 2003 10:56:53 -0400 (EDT) [thread overview]
Message-ID: <54490.141.155.88.179.1066143413.squirrel@minsky-primus.homeip.net> (raw)
In-Reply-To: <51792.141.155.88.179.1066142234.squirrel@minsky-primus.homeip.net>
Here's a working solution, I think.
let raw_min = min
let raw_max = max
let nan_or_equal x y =
not (x < y) && not (x > y)
(** min and max that choose nan if its there *)
let min x y =
if x = y then x
else if nan_or_equal x y then nan
else raw_min x y
let max x y =
if x = y then x
else if nan_or_equal x y then nan
else raw_max x y
> min and max have pretty strange behavior when it comes to nan's. Here's
> an example:
>
> # min 3. nan;;
> - : float = 3.
> # min nan 3.;;
> - : float = nan
>
> When you think about it, the reason for this is clear. comparisons
> involving nan's always return false, so if you simply implement min as
> follows:
>
> if x < y then x else y
>
> the the result will depend on the order.
>
> Now here's the weird bit. I decided I wanted a polymorphic comparison
> that wouldn't have this problem. But this is a little harder than it
> seems, since it turns out that specialized float version of equality is
> different from the polymorphic version. Here's the example:
>
> # let raw_min = min
> val raw_min : 'a -> 'a -> 'a = <fun>
> # let min x y =
> if not (y = y) then y
> else if not (x = x) then x
> else raw_min x y
> ;;
> val min : 'a -> 'a -> 'a = <fun>
> # let fmin (x:float) y =
> if not (y = y) then y
> else if not (x = x) then x
> else raw_min x y
> ;;
> val fmin : float -> float -> float = <fun>
> # fmin 3. nan;;
> - : float = nan
> # fmin nan 3.;;
> - : float = nan
> # min nan 3.;;
> - : float = nan
> # min 3. nan;;
> - : float = 3.
>
> So, does this count as a bug? Any ideas about how to fix this behavior in
> a reasonably efficient way?
>
> Yaron
>
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr Archives:
> http://caml.inria.fr
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ:
> http://caml.inria.fr/FAQ/
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-10-14 14:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 14:37 Yaron Minsky
2003-10-14 14:56 ` Yaron Minsky [this message]
2003-10-14 20:52 ` Yaron Minsky
2003-10-14 23:43 ` skaller
2003-10-16 17:29 ` Hendrik Tews
2003-10-16 13:16 ` Xavier Leroy
2003-10-16 14:01 ` Yaron Minsky
2003-10-17 9:26 ` [Caml-list] Test nan (was: Weird behavior with nan's and min/max) Christophe TROESTLER
2003-10-16 21:40 ` [Caml-list] Weird behavior with nan's and min/max Yaron Minsky
2003-10-16 21:50 ` Yaron Minsky
2003-10-16 22:52 ` Damien Doligez
2003-10-17 14:55 ` skaller
2003-10-17 15:14 ` Floating point exceptions (Was Re: [Caml-list] Weird behavior with nan's and min/max) Yaron Minsky
2003-10-17 23:55 ` [Caml-list] Weird behavior with nan's and min/max Yaron M. Minsky
2003-10-20 13:29 ` Xavier Leroy
2003-10-20 13:43 ` Yaron Minsky
2003-10-20 14:24 ` Xavier Leroy
2003-10-16 23:55 ` [Caml-list] " Jed Davis
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=54490.141.155.88.179.1066143413.squirrel@minsky-primus.homeip.net \
--to=yminsky@cs.cornell.edu \
--cc=caml-list@inria.fr \
/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