From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Libvirt <libvir-list@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: A brief look at deprecating our JSON extensions over RFC 8259
Date: Tue, 23 Feb 2021 13:43:49 +0100 [thread overview]
Message-ID: <87sg5nc5tm.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA_NNyFM=bqN663o3r49tgpa21U9Easv9=EXzqW1Ygfqhg@mail.gmail.com> (Peter Maydell's message of "Tue, 23 Feb 2021 11:03:19 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> On Tue, 23 Feb 2021 at 09:33, Markus Armbruster <armbru@redhat.com> wrote:
>> Misunderstanding: our JSON interpolation feature is *not* string
>> interpolation! It interpolates *objects* into the QObject built by the
>> parser.
>
> Given that it's basically undocumented except in a scattered
> handful of comments inside the qjson parser implementation, it's
> not too surprising that people misunderstand it :-)
Yes, that's fair.
I added a fair amount of commentary, but it's heavily geared towards
maintainers, not users.
> (One surprising
> feature: the parser takes ownership of the object that you pass it
> via the '%p' interpolation, and will qobject_unref() it.)
Yes, %p takes over the reference.
next prev parent reply other threads:[~2021-02-23 12:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 14:57 A brief look at deprecating our JSON extensions over RFC 8259 Markus Armbruster
2021-02-22 15:10 ` Peter Krempa
2021-02-22 15:24 ` Daniel P. Berrangé
2021-02-22 15:43 ` Liviu Ionescu
2021-02-22 17:47 ` Paolo Bonzini
2021-02-22 17:54 ` Daniel P. Berrangé
2021-02-22 18:06 ` Paolo Bonzini
2021-02-23 9:31 ` Markus Armbruster
2021-02-23 9:37 ` Markus Armbruster
2021-02-23 11:03 ` Peter Maydell
2021-02-23 12:43 ` Markus Armbruster [this message]
2021-02-23 9:06 ` Markus Armbruster
2021-02-23 10:59 ` Paolo Bonzini
2021-02-23 12:34 ` Markus Armbruster
2021-02-22 17:42 ` Paolo Bonzini
2021-02-22 18:01 ` Daniel P. Berrangé
2021-02-22 18:22 ` Peter Krempa
2021-02-22 18:25 ` Peter Krempa
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=87sg5nc5tm.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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.