All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, 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 06:47:12 -0600	[thread overview]
Message-ID: <4B5EE450.9090004@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100126094329.70719b6f@doriath>

On 01/26/2010 05:43 AM, Luiz Capitulino wrote:
>> The issue I see isn't related to unsigned.  Apparently we currently
>> accept values such as 'a' as valid strings. Since this is not valid json
>> we probably should reject it just in case we will want to switch to
>> another json library, otherwise clients might come to depend on
>> non-standard behaviour.
>>      
>   This extension is only used internally by QEMU and we find it
> very convenient otherwise we would have to escape strings in
> dicts and lists, which is error prone and time consuming.
>    

Actually, I was reading the JSON RFC last night and came across:

   "A JSON parser transforms a JSON text into another representation. A
    JSON parser MUST accept all texts that conform to the JSON grammar.
    A JSON parser MAY accept non-JSON forms or extensions."

So we are fully JSON compliant in our current implementation.

Regards,

Anthony Liguori

  parent reply	other threads:[~2010-01-26 12:47 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 [this message]
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
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=4B5EE450.9090004@linux.vnet.ibm.com \
    --to=aliguori@linux.vnet.ibm.com \
    --cc=armbru@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 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.