From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"Viet Le" <vietlq85@gmail.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Float precision in OCaml
Date: Wed, 2 Aug 2017 08:22:12 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A175B282CDD@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <etPan.5980c2fb.784900a1.123@erratique.ch>
Dear Daniel,
> And since you have no control on which binary to decimal codecs JSON parsers
> are going to use you have absolutely no interoperability story at that point.
this is true, although if both ends use "round trip safe" codecs, the error should be at most 1 LSB and this also only in rare cases, which is at least a bit of a story. If one uses codecs which are not round trip safe, the story is much worse. So I would say that using round trip safe codecs still gives a substantial advantage. But you are definitely right - it is not the holy grail.
It would be an interesting exercise to test the interoperability of different round trip safe codecs.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2017-08-02 8:22 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0F7D3B1B3C4B894D824F5B822E3E5A175B282CDD@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
--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).