caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Viet Le <vietlq85@gmail.com>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Float precision in OCaml
Date: Tue, 1 Aug 2017 15:17:36 +0200	[thread overview]
Message-ID: <etPan.59807f70.67b01df4.123@erratique.ch> (raw)
In-Reply-To: <etPan.59807b8a.db32dee.123@AirmailxGenerated.am>

On 1 August 2017 at 14:56:23, Viet Le (vietlq85@gmail.com) wrote:
> Thanks Daniel and François for pointing out the RFC
> https://tools.ietf.org/html/rfc7159 and mentioning IEEE 754-2008 binary64.
> For my JSON parser I use Int64 to store integers and float to store
> decimal/floating point values. The tweak gives nice feature and helps with
> round-trip encoding/decoding.

I wouldn't do this; you'll get into interoperability problems, other parsers (e.g. JSON.parse) won't be able to read all the ints you are serialize via these Int64.t values, they will be represented unprecisely. Stick to [-2^53;2^53] for ints and use floats to represent them, this will force users of the codec to think about the problem. 

Here's what parsing 2^53+1 gives in my browser:

 JSON.parse('9007199254740993')
 9007199254740992

If you want to represent full Int64.t values in JSON choose a textual representation for it and serialize to a string.

Best, 

Daniel

  parent reply	other threads:[~2017-08-01 13:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 10:47 Viet Le
2017-08-01 11:18 ` Nicolás Ojeda Bär
2017-08-01 11:25   ` Frédéric Bour
2017-08-01 11:45     ` Viet Le
2017-08-01 11:40   ` François Bobot
2017-08-01 11:42   ` Viet Le
2017-08-01 11:48     ` François Bobot
2017-08-01 12:12 ` Daniel Bünzli
2017-08-01 12:56   ` Viet Le
     [not found]   ` <etPan.59807b8a.db32dee.123@AirmailxGenerated.am>
2017-08-01 13:17     ` Daniel Bünzli [this message]
2017-08-01 13:57   ` Soegtrop, Michael
2017-08-01 14:07     ` Soegtrop, Michael
2017-08-01 15:48     ` Peter Thiemann
2017-08-01 17:12       ` Soegtrop, Michael
2017-08-02  7:41         ` Peter Thiemann
     [not found]   ` <etPan.5980c173.1234cb4.123@AirmailxGenerated.am>
2017-08-01 18:05     ` Daniel Bünzli
2017-08-02  5:46       ` Viet Le
2017-08-02  8:22       ` Soegtrop, Michael

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=etPan.59807f70.67b01df4.123@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    --cc=vietlq85@gmail.com \
    /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).