From: Andreas Rossberg <rossberg@ps.uni-sb.de>
To: Caml Mailing List <caml-list@inria.fr>
Cc: Christian Lindig <lindig@eecs.harvard.edu>,
George Russell <ger@informatik.uni-bremen.de>
Subject: Re: NaN Test in OCaml
Date: Thu, 01 Feb 2001 10:58:18 +0100 [thread overview]
Message-ID: <3A79333A.E447EF42@ps.uni-sb.de> (raw)
In-Reply-To: <20010131140503.D2418@lakeland.eecs.harvard.edu>
Christian Lindig wrote:
>
> George Russell <ger@informatik.uni-bremen.de> has suggested on
> comp.lang.ml the following test to find out whether a float is NaN:
>
> x is not a NaN <=> (x = x)
>
> Doing this leads to interesting results with OCaml 3.0:
>
> # let nan x = not (x = x);;
> val nan : 'a -> bool = <fun>
> # nan (1.0 /. 0.0);;
> - : bool = false (* correct *)
> # nan (0.0 /. 0.0);;
> - : bool = false (* should be true *)
>
> The following definition of nan uses a type annotation and has a
> different result:
>
> # let nan (x:float) = not (x = x);;
> val nan : float -> bool = <fun>
> # nan (0.0 /. 0.0);;
> - : bool = true (* correct *)
> # nan (1.0 /. 0.0);;
> - : bool = false (* correct *)
Right, because the first example uses polymorphic equality which is
purely structural. The second uses proper floating point comparison.
Actually, what we have here, is a subtle kind of overloading. Subtle in
particular because it is overlapping. IMHO it would be preferable if
floating point comparison used different syntax, probably "=.". In that
case the compiler should probably emit a warning whenever he discovered
the use of structural equality on floats.
--
Andreas Rossberg, rossberg@ps.uni-sb.de
:: be declarative. be functional. just be. ::
next prev parent reply other threads:[~2001-02-02 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 19:05 Christian Lindig
2001-02-01 9:19 ` David Mentre
2001-02-01 9:58 ` Andreas Rossberg [this message]
2001-02-01 14:41 ` Xavier Leroy
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=3A79333A.E447EF42@ps.uni-sb.de \
--to=rossberg@ps.uni-sb.de \
--cc=caml-list@inria.fr \
--cc=ger@informatik.uni-bremen.de \
--cc=lindig@eecs.harvard.edu \
/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 NNTP newsgroup(s).