caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Christophe Raffalli <Christophe.Raffalli@univ-savoie.fr>
To: Sean McLaughlin <seanmcl@cmu.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] float rounding
Date: Tue, 03 Oct 2006 21:59:45 +0200	[thread overview]
Message-ID: <4522C131.9010400@univ-savoie.fr> (raw)
In-Reply-To: <89957A27-4B6A-4FCF-A425-1468ECFA8B62@cmu.edu>

Sean McLaughlin a écrit :
> Hello,
>
>   I'm using Ocaml for an interval arithmetic application.  I"m curious 
> about
> what the Ocaml parser/compiler does to float constants.  May I assume
> that for any constant I enter, eg. 3.1415... (for N digits of pi), that
> the compiler will give me a closest machine representable number?
> i.e., if I bound a constant by the previous and next floating point 
> value to
> that given me by the compiler,
> will it always be the case that my original (mathematical) constant 
> lies in that interval?
>

By the way, float constants need to be written in hexadecimal and this 
is missing to
the printf/scanf functions (it is what man printf says at least) ... 
just compute how many decimals you need to write the exact value of 
2^{-n} as a decimal float constant (0,5 0,25 0,125 0,625e-1 0,3125e-1 ...).

Then, I am not sure  the algorithm used to parse the constant will give 
you the correct value and you will never know how many decimals you need 
to write your constant.

The only problem with float and hexadecimal is to learn the hexadecimals 
of pi, e, ln 2, sqrt 2, ... ;-)

Christophe Raffalli


  parent reply	other threads:[~2006-10-03 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30 18:25 Sean McLaughlin
2006-10-01 12:44 ` [Caml-list] " Florent Monnier
2006-10-01 13:36 ` Gerd Stolpmann
2006-10-01 16:36 ` Xavier Leroy
2006-11-23 23:00   ` David Monniaux
2006-10-03 13:41 ` Christophe Raffalli
2006-10-03 19:59 ` Christophe Raffalli [this message]
2006-10-03 21:05   ` Olivier Andrieu
2006-11-26  1:51     ` David Monniaux

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=4522C131.9010400@univ-savoie.fr \
    --to=christophe.raffalli@univ-savoie.fr \
    --cc=caml-list@inria.fr \
    --cc=seanmcl@cmu.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).