From: Drew Adams <drew.adams@oracle.com>
To: Jimmy Yuen Ho Wong <wyuenho@gmail.com>, 42994@debbugs.gnu.org
Subject: bug#42994: 27.1; json-serialize unable to serialize JSON values
Date: Sun, 23 Aug 2020 09:58:14 -0700 (PDT) [thread overview]
Message-ID: <9105c19a-e812-4c79-b1b9-cc77fabb2faa@default> (raw)
In-Reply-To: <4309c1ca-f568-2fb4-cba0-d6e86453a94c@gmail.com>
> I'm not sure why you are bringing this up. Even RFC 8259 is 3 years old
> and prior to that people had been sending booleans strings and numbers
> as JSON text for many years.
I'm actually agreeing with you.
I brought it up to point out that at one time
JSON scalar values were typically not considered
to be JSON texts. This explains why some systems,
frameworks, applications, etc. might not support
scalar serialization.
That's all. I do believe that Emacs should
support RFC 8259 (it should always support the
latest JSON specs). And it should support it
by default.
For interoperability with other systems etc. that
do not support scalar texts, it can be useful to
have a mode that, likewise, doesn't support/allow
scalars as JSON texts - e.g., a "disable scalars"
mode, which rejects a document that isn't an
object or an array.
But by default Emacs should support scalar texts.
next prev parent reply other threads:[~2020-08-23 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 12:24 bug#42994: 27.1; json-serialize unable to serialize JSON values Jimmy Yuen Ho Wong
2020-08-23 12:53 ` Eli Zaretskii
2020-08-23 12:56 ` Jimmy Yuen Ho Wong
2020-08-23 14:05 ` Jimmy Yuen Ho Wong
2020-08-23 16:21 ` Drew Adams
2020-08-23 16:46 ` Jimmy Yuen Ho Wong
2020-08-23 16:58 ` Drew Adams [this message]
2020-08-24 6:13 ` Jimmy Yuen Ho Wong
2021-02-13 13:40 ` Philipp
2021-02-13 18:23 ` Basil L. Contovounesios
2021-02-13 18:36 ` Philipp
2021-02-13 23:30 ` bug#42994: [External] : " Drew Adams
2021-02-14 0:40 ` Jimmy Yuen Ho Wong
2021-02-14 10:00 ` Philipp Stephani
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=9105c19a-e812-4c79-b1b9-cc77fabb2faa@default \
--to=drew.adams@oracle.com \
--cc=42994@debbugs.gnu.org \
--cc=wyuenho@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).