all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Drew Adams <drew.adams@oracle.com>,
	"Theresa O'Connor" <hober0@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: two json.el bugs
Date: Sun, 28 May 2017 18:47:27 +0000	[thread overview]
Message-ID: <CAArVCkRGeubLsJFNjdL_-6wD7Ww62boJ_j40DCb253CBJpXm6A@mail.gmail.com> (raw)
In-Reply-To: <16aabb87-3130-41b8-968e-52bc5aea3956@default>

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

Drew Adams <drew.adams@oracle.com> schrieb am So., 28. Mai 2017 um
03:30 Uhr:

> > We can't simply serialize/desterialize alists in key order
> > because the order is reversed in Emacs. (In Emacs alists,
> > if there are duplicates, the first one wins,
> > in JSON the last one wins.)
>   ^^^^^^^^^^^^^^^^^^^^^^^^^
>
> If you're talking about JSON objects then no, no particular
> meaning or behavior is defined for duplicate fields (keys)
> in a JSON object.
>
> A given application that handles JSON object is free to
> act as you say.  And it is free to act otherwise.
>

Please see Theresa's initial post why this matters.

[-- Attachment #2: Type: text/html, Size: 963 bytes --]

  reply	other threads:[~2017-05-28 18:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 17:51 two json.el bugs Theresa O'Connor
2017-05-05 18:44 ` Yuri Khan
2017-05-05 19:25   ` Drew Adams
2017-05-20 15:51   ` [PATCH] Fix definition of whitespace in JSON Philipp Stephani
2017-05-20 17:28     ` Dmitry Gutov
2017-05-21 21:03       ` Philipp Stephani
2017-05-27 13:32   ` two json.el bugs Philipp Stephani
2017-05-27 13:48 ` Philipp Stephani
2017-05-28  1:30   ` Drew Adams
2017-05-28 18:47     ` Philipp Stephani [this message]
2017-05-28 22:12       ` Drew Adams
2017-05-28 22:44         ` Bruce V Chiarelli
2017-05-29  0:42           ` Drew Adams

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=CAArVCkRGeubLsJFNjdL_-6wD7Ww62boJ_j40DCb253CBJpXm6A@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=hober0@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 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.