From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
Herve Poussineau <hpoussin@reactos.org>,
Markus Armbruster <armbru@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] win32: use PRId64 instead of %lld
Date: Tue, 26 Jan 2010 08:38:03 -0600 [thread overview]
Message-ID: <4B5EFE4B.7070109@codemonkey.ws> (raw)
In-Reply-To: <4B5EF856.4050006@redhat.com>
On 01/26/2010 08:12 AM, Avi Kivity wrote:
> On 01/26/2010 04:05 PM, Anthony Liguori wrote:
>> On 01/26/2010 07:55 AM, Avi Kivity wrote:
>>> The risk is that if we support a private extension (like '') and
>>> then json is officially extended to support a conflicting or similar
>>> syntax with a different meaning, then we cannot advance to the next
>>> revision of json without breaking compatibility.
>>
>> The paragraph I quoted from the RFC seems to suggest that the authors
>> of JSON boxed themselves in with respect to extending JSON. The
>> reason being that a conforming implementation is given free reign to
>> extend with "non-JSON forms or extensions". That would seem to
>> prevent any extension.
>
> A json generator is required to generate conforming text. So there
> are three choices:
>
> - reject 's
> - unofficially accept 's, nonconforming generators break if json
> changes, nor our problem
> - officially accept 's, look stupid when json changes
>
>>
>> Keep in mind, JSON is a proper subset of ECMAScript which means the
>> likelihood of extension going outside of ECMAScript would be
>> extremely unlikely. I don't expect JSON is ever going to change.
>
> Who knows? Let's not take unnecessary risks.
Keep in mind, I've already agreed to not allow '' strings for external
JSON. The only reason the thread's still alive is because we like to
argue apparently :-) Single quoted strings are not sufficiently useful
to warrant taking any risks here.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-01-26 14:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 21:23 [Qemu-devel] [PATCH] win32: use PRId64 instead of %lld Herve Poussineau
2010-01-25 10:09 ` [Qemu-devel] " Michael S. Tsirkin
2010-01-25 14:03 ` Luiz Capitulino
2010-01-25 14:35 ` Markus Armbruster
2010-01-25 15:27 ` Luiz Capitulino
2010-01-25 15:38 ` Michael S. Tsirkin
2010-01-26 11:43 ` Luiz Capitulino
2010-01-26 12:37 ` Markus Armbruster
2010-01-26 12:56 ` Anthony Liguori
2010-01-26 12:56 ` Michael S. Tsirkin
2010-01-26 13:05 ` Anthony Liguori
2010-01-26 13:12 ` Michael S. Tsirkin
2010-01-26 12:47 ` Anthony Liguori
2010-01-26 12:46 ` Michael S. Tsirkin
2010-01-26 12:58 ` Anthony Liguori
2010-01-26 13:01 ` Michael S. Tsirkin
2010-01-26 13:13 ` Anthony Liguori
2010-01-26 13:08 ` Daniel P. Berrange
2010-01-26 13:15 ` Anthony Liguori
2010-01-26 13:55 ` Avi Kivity
2010-01-26 14:05 ` Anthony Liguori
2010-01-26 14:12 ` Avi Kivity
2010-01-26 14:38 ` Anthony Liguori [this message]
2010-01-25 17:32 ` Stefan Weil
2010-01-25 17:47 ` Michael S. Tsirkin
2010-01-25 19:23 ` Stefan Weil
2010-01-25 19:32 ` Michael S. Tsirkin
2010-01-25 19:34 ` Michael S. Tsirkin
2010-01-25 19:51 ` Daniel P. Berrange
2010-01-25 19:41 ` Stefan Weil
2010-01-26 22:40 ` [Qemu-devel] " Anthony Liguori
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=4B5EFE4B.7070109@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=hpoussin@reactos.org \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.
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 NNTP newsgroup(s).