From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
To: Drew Adams <drew.adams@oracle.com>,
"Basil L. Contovounesios" <contovob@tcd.ie>,
"p.stephani2@gmail.com" <p.stephani2@gmail.com>
Cc: "42994@debbugs.gnu.org" <42994@debbugs.gnu.org>
Subject: bug#42994: [External] : bug#42994: 27.1; json-serialize unable to serialize JSON values
Date: Sun, 14 Feb 2021 00:40:05 +0000 [thread overview]
Message-ID: <b1de8e7a-c647-aad0-729b-aa26b260fae2@gmail.com> (raw)
In-Reply-To: <SA2PR10MB4474E51BCC2759113648A1BAF38A9@SA2PR10MB4474.namprd10.prod.outlook.com>
If the original intention for `json-serialize` was to offer a
functionally equivalent native version of `json-encode`, then this is a
bug. There was no discussion about this mismatch whatsover, so my guess
is this was an omission and thus a bug.
On 13/02/2021 11:30 PM, Drew Adams wrote:
>> Thanks! Does this need calling out in etc/NEWS, or is it considered
>> more of a bugfix?
> (Again, not really following this thread.)
>
> If Emacs support of JSON parsing or serializing
> changes from considering only objects and arrays
> to be "jsons" to considering also JSON scalars
> to be "jsons", then that's not a bug fix; it's
> a change in support of the JSON language. IMO,
> that should be called out somewhere such as NEWS.
next prev parent reply other threads:[~2021-02-14 0:40 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
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 [this message]
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=b1de8e7a-c647-aad0-729b-aa26b260fae2@gmail.com \
--to=wyuenho@gmail.com \
--cc=42994@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=drew.adams@oracle.com \
--cc=p.stephani2@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).