From: Amos Kong <akong@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: lcapitulino@redhat.com, qemu-devel@nongnu.org,
aliguori@amazon.com, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] qapi: store raw expressions to QAPISchema
Date: Thu, 23 Jan 2014 19:53:59 +0800 [thread overview]
Message-ID: <20140123115359.GA14603@amosk.info> (raw)
In-Reply-To: <87fvof7yvv.fsf@blackfin.pond.sub.org>
On Thu, Jan 23, 2014 at 11:53:24AM +0100, Markus Armbruster wrote:
> Amos Kong <akong@redhat.com> writes:
>
> > After cleaning up the comments of qapi-schema.json file, we get
> > an range of raw expressions, they are also converted to ordered
> > dictionaries.
> >
> > This patch just addes a member to QAPISchema to store the raw
> > expressions.
> >
> > Actually this patch was split from QMP introspection patchset,
> > it's no longer needed in that patchset. I would like to post
> > this patch singly, we can apply it if it's useful.
>
> It'll be useful when it has a user, or if it eases maintenance. Neither
> is obvious to me at a quick, superficial glance.
The patch didn't change original parse logic, it just repeatedly
save each single clear schema to a list in existed loop. I think
it's easy to maintain.
In the introspection patchset, I want to pass raw json expressions
to C code by a head file, then convert the json expressions to
qobject, then ...
At the end, I generated a expression with more metadata when visit
Ordered Dictionaries. So raw expressions were not used.
> Happy to hear a more verbose explanation of what raw expressions might
> be good for.
--
Amos.
prev parent reply other threads:[~2014-01-23 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 7:30 [Qemu-devel] [PATCH] qapi: store raw expressions to QAPISchema Amos Kong
2014-01-23 10:53 ` Markus Armbruster
2014-01-23 11:53 ` Amos Kong [this message]
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=20140123115359.GA14603@amosk.info \
--to=akong@redhat.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).