From: Eli Zaretskii <eliz@gnu.org>
To: "Géza Herman" <geza.herman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Improving JSON pretty printing, how to represent floats?
Date: Fri, 05 Apr 2024 16:09:53 +0300 [thread overview]
Message-ID: <867chc5526.fsf@gnu.org> (raw)
In-Reply-To: <87bk6o55ci.fsf@gmail.com> (message from Herman, Géza on Fri, 05 Apr 2024 14:55:26 +0200)
> From: Herman, Géza <geza.herman@gmail.com>
> Cc: Géza Herman <geza.herman@gmail.com>,
> emacs-devel@gnu.org
> Date: Fri, 05 Apr 2024 14:55:26 +0200
>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > The digits in 3.333333333333000000000000000001 after 16th digit
> > are meaningless: they aren't supported by IEEE floating-point
> > standard, so they are just numerical noise. Thus, talking about
> > "lossless" wrt them makes little sense to me.
>
> You mean the 64-bit binary format. IEEE-754 describes more formats
> which have more precision, and also there are more formats used in
> practice than what IEEE-754 describes.
>
> Plus, I don't think that the JSON standard mandates IEEE-754
> numbers. It just describes numbers, so I think it's good behavior
> to not change numbers during formatting.
The fact that Emacs supports IEEE-754 on almost all platforms is
prominently documented in the ELisp reference manual, see the node
"Float Basics" there.
next prev parent reply other threads:[~2024-04-05 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 9:39 Improving JSON pretty printing, how to represent floats? Herman, Géza
2024-04-05 12:35 ` Eli Zaretskii
2024-04-05 12:53 ` Mattias Engdegård
2024-04-05 12:55 ` Herman, Géza
2024-04-05 13:09 ` Eli Zaretskii [this message]
2024-04-05 13:16 ` Herman, Géza
2024-04-05 14:01 ` tomas
2024-04-05 15:34 ` Eli Zaretskii
2024-04-05 16:46 ` Herman, Géza
2024-04-05 13:37 ` Dmitry Gutov
2024-04-05 14:20 ` Herman, Géza
2024-04-05 16:47 ` Dmitry Gutov
2024-04-05 14:18 ` Mattias Engdegård
2024-04-05 14:25 ` Herman, Géza
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=867chc5526.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=geza.herman@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).