bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>, bug-gnulib@gnu.org
Subject: Re: Easy Accurate Reading and Writing of Floating-Point Numbers
Date: Wed, 20 May 2020 12:04:00 +0200	[thread overview]
Message-ID: <CAEYrNrTjqgEmp=3PJerRkFJAzUTQUT=nLh7un1bhEh8HB=Rq+A@mail.gmail.com> (raw)
In-Reply-To: <9817931.4WPAKDlFbJ@omega>

Am Mi., 20. Mai 2020 um 00:37 Uhr schrieb Bruno Haible <bruno@clisp.org>:

> Marc Nieper-Wißkirchen wrote:
> > for output, the shortest rounded
> > representation that still reads back accurately has to be selected.
> > ...
> > A simple algorithm is given by Aubrey Jaffer in [1].
> >
> > [1] http://people.csail.mit.edu/jaffer/III/EZFPRW

This was just one, which I liked because of its simplicity. (And
because it is written in my favorite programming language.)

[...]

> There are several other algorithms for this purpose.

There is also the new Ryu algorithm by Ulf Adams, see [2].
Interestingly, he has found some problems in Jaffer's algorithm, see
the paper [3].

[...]

> Then there's also the algorithm, by Michael Stoll and me (1990),
> in GNU clisp and CLN (based on multiprecision arithmetic, not hardware floats).

I didn't know this; I will check this out.

The initial version of "c_dtoastr" will, however just work as "dtoastr" does.

Marc

--

[2] https://github.com/ulfjack/ryu

[3] https://dl.acm.org/doi/10.1145/3296979.3192369


      reply	other threads:[~2020-05-20 10:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19  7:44 Easy Accurate Reading and Writing of Floating-Point Numbers Marc Nieper-Wißkirchen
2020-05-19 15:10 ` Marc Nieper-Wißkirchen
2020-05-19 15:35   ` Marc Nieper-Wißkirchen
2020-05-19 15:51     ` Paul Eggert
2020-05-19 16:11       ` Marc Nieper-Wißkirchen
2020-05-19 17:23         ` Tim Rühsen
2020-05-19 19:10           ` Marc Nieper-Wißkirchen
2020-05-19 21:25             ` Tim Rühsen
2020-05-19 22:15             ` copyright in Germany Bruno Haible
2020-05-20  9:52               ` Marc Nieper-Wißkirchen
2020-05-20 13:41                 ` Bruno Haible
2020-05-20 12:39       ` Easy Accurate Reading and Writing of Floating-Point Numbers Marc Nieper-Wißkirchen
2020-05-23 12:02         ` Bruno Haible
2020-05-23 12:26           ` Marc Nieper-Wißkirchen
2020-05-23 14:52             ` Bruno Haible
2020-05-23 15:50               ` Marc Nieper-Wißkirchen
2020-05-23 15:33             ` Paul Eggert
2020-06-25 19:19           ` Bruno Haible
2020-06-25 19:33             ` Marc Nieper-Wißkirchen
2020-05-19 22:37 ` Bruno Haible
2020-05-20 10:04   ` Marc Nieper-Wißkirchen [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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEYrNrTjqgEmp=3PJerRkFJAzUTQUT=nLh7un1bhEh8HB=Rq+A@mail.gmail.com' \
    --to=marc.nieper+gnu@gmail.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).