From: Drew Adams <drew.adams@oracle.com>
To: Philipp <p.stephani2@gmail.com>, Thomas Hisch <thomas.hisch@ims.co.at>
Cc: "46486@debbugs.gnu.org" <46486@debbugs.gnu.org>
Subject: bug#46486: [External] : bug#46486: 28.0.50; json-parse-string missing support for key-less json strings
Date: Sat, 13 Feb 2021 23:22:43 +0000 [thread overview]
Message-ID: <SA2PR10MB447449ABCDDFC56965710579F38A9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <C628B249-1696-49C4-99A5-AB231E74E70B@gmail.com>
> OTOH, RFC 8259 does seem to allow any value type at the toplevel now,
> so we might as well support this. I don’t have a strong opinion here.
> Using RFC 4627 semantics seems a bit safer and more conservative, but
> given that it’s considered obsoleted by RFC 8259, maybe we should
> switch to the semantics of the newer standard.
Sorry, my previous comment duplicates what you just said.
IMO, nowadays applications should generally
consider all possible JSON values as JSON
texts: objects, arrays, and scalars.
next prev parent reply other threads:[~2021-02-13 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 12:04 bug#46486: 28.0.50; json-parse-string missing support for key-less json strings Thomas Hisch
2021-02-13 12:08 ` bug#46486: (no subject) Thomas Hisch
2021-02-13 12:24 ` bug#46486: 28.0.50; json-parse-string missing support for key-less json strings Philipp
2021-02-13 12:33 ` Philipp
2021-02-13 23:22 ` Drew Adams [this message]
2021-02-13 12:35 ` Basil L. Contovounesios
2021-02-13 23:20 ` bug#46486: [External] : " Drew Adams
2021-02-13 12:30 ` Basil L. Contovounesios
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=SA2PR10MB447449ABCDDFC56965710579F38A9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=46486@debbugs.gnu.org \
--cc=p.stephani2@gmail.com \
--cc=thomas.hisch@ims.co.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.