From: Nicolas Petton <nicolas@petton.fr>
To: Damien Cassou <damien@cassou.me>,
Yoichi Nakayama <yoichi.nakayama@gmail.com>
Cc: Philipp Stephani <phst@google.com>,
Mark Oteiza <mvoteiza@udel.edu>,
Theresa O'Connor <ted@oconnor.cx>,
24252@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#24252: 25.1; json.el doesn't distinguish null and empty object
Date: Mon, 28 May 2018 17:21:46 +0200 [thread overview]
Message-ID: <877enniz5h.fsf@petton.fr> (raw)
In-Reply-To: <87o9hci1c5.fsf@cassou.me>
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
Damien Cassou <damien@cassou.me> writes:
> please find a patch attached. This patch uses :json-null to distinguish,
> during pretty-print, between the value null and an empty object.
It looks good to me, but I'm wondering if encoding/decoding (not
pretty-printing) will be backward-compatible or not.
Cheers,
Nico
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-05-28 15:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 14:54 bug#24252: 25.1; json.el doesn't distinguish null and empty object Yoichi Nakayama
2016-08-19 2:06 ` Dmitry Gutov
2016-08-19 23:45 ` Yoichi Nakayama
2016-08-20 0:52 ` Dmitry Gutov
2016-08-20 6:12 ` Yoichi Nakayama
2016-08-21 1:30 ` Yoichi Nakayama
2016-08-21 3:42 ` Dmitry Gutov
2016-08-21 12:11 ` Yoichi Nakayama
2016-08-21 13:32 ` Yoichi Nakayama
2016-08-21 15:06 ` Yoichi Nakayama
2016-08-27 0:05 ` Dmitry Gutov
2018-05-17 14:39 ` Damien Cassou
2018-05-19 6:52 ` Damien Cassou
2018-05-28 15:21 ` Nicolas Petton [this message]
2018-06-11 13:36 ` Damien Cassou
2018-06-12 17:14 ` Eli Zaretskii
2018-06-13 7:13 ` Damien Cassou
2018-06-13 13:05 ` Nicolas Petton
2018-06-13 16:55 ` Eli Zaretskii
2018-06-14 9:04 ` Nicolas Petton
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=877enniz5h.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=24252@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=dgutov@yandex.ru \
--cc=mvoteiza@udel.edu \
--cc=phst@google.com \
--cc=ted@oconnor.cx \
--cc=yoichi.nakayama@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).