From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori@us.ibm.com, Herve@gnu.org,
Poussineau <hpoussin@reactos.org>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] win32: use PRId64 instead of %lld
Date: Mon, 25 Jan 2010 13:27:19 -0200 [thread overview]
Message-ID: <20100125132719.23a483cf@doriath> (raw)
In-Reply-To: <m3k4v6s14m.fsf@blackfin.pond.sub.org>
On Mon, 25 Jan 2010 15:35:53 +0100
Markus Armbruster <armbru@redhat.com> wrote:
> Luiz Capitulino <lcapitulino@redhat.com> writes:
>
> > On Mon, 25 Jan 2010 12:09:06 +0200
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> [...]
> >> Finally,
> >> don't we want unsigned values in protocol?
> >
> > JSON doesn't support them.
>
> Uh, where does the RFC say that?
I see that my comment was misleading.
In JSON we don't have unsigned types, we have only a type
called 'number' to represent them all.
Unsigneds should be handled correctly, except for uint64_t which
is cast to int64_t.
Michael, does this answer your question? Is there any
issue with the handling of unsigneds I'm not aware about?
next prev parent reply other threads:[~2010-01-25 15:27 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 [this message]
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
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=20100125132719.23a483cf@doriath \
--to=lcapitulino@redhat.com \
--cc=Herve@gnu.org \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=hpoussin@reactos.org \
--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).