unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: "Herman, Géza" <geza.herman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Improving JSON pretty printing, how to represent floats?
Date: Fri, 5 Apr 2024 19:47:13 +0300	[thread overview]
Message-ID: <8fb065f1-fd9f-492d-a183-13b2019a233e@gutov.dev> (raw)
In-Reply-To: <8734rz6g8v.fsf@gmail.com>

On 05/04/2024 17:20, Herman, Géza wrote:
> 
> Dmitry Gutov <dmitry@gutov.dev> writes:
> 
>> On 05/04/2024 12:39, Herman, Géza wrote:
>>> What would be the best representation for numbers in this case? I'm 
>>> thinking about using symbols, but I'm not sure this is the
>>> best approach.  The parser/encoder would have a new keyword 
>>> parameter, like ":numbers-as-symbols t".  If this is specified, then
>>> numbers wouldn't be parsed, but kept as symbols.  What do you think, 
>>> is this a good approach?
>>
>> Why not just use strings? Bignum implementations in various libs 
>> (other languages) often use strings in constructors.
> 
> Because then the original type is lost: Later it's not possible to tell 
> whether a value was a number or a string originally.
> 
>>
>> Interning numbers in obarray doesn't seems like too great an idea.
> 
> That's correct, my idea is to use uninterned symbols (make-symbol).

Okay, then that's not a problem. You could use a more complex type (like 
a struct), but that doesn't seem urgent.

OTOH, Mattias also has a point that high performance is not as important 
here, and maybe a Lisp implementation would be preferable over adding a 
slightly clunkier interface to the parser function.



  reply	other threads:[~2024-04-05 16:47 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
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 [this message]
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=8fb065f1-fd9f-492d-a183-13b2019a233e@gutov.dev \
    --to=dmitry@gutov.dev \
    --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).