From: Wang Dong <dongdwdw@linux.vnet.ibm.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] new to qemu with a simple question
Date: Wed, 24 May 2017 16:37:58 +0800 [thread overview]
Message-ID: <d68094a6-574e-9bb7-5574-298285ac477c@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170524031141.GI12279@lemon.lan>
Thank you, Fam.
On 05/24/2017 11:11 AM, Fam Zheng wrote:
> On Wed, 05/24 10:56, Wang Dong wrote:
>> Some C source code is generate from json file.
>>
>> I wonder why this? What is the benefits of this?
> This allows you to concentrate on the high level semantics of the QMP API,
> without worrying about C syntax and structural code here and there. In one
> word, more conciseness and little code duplication.
>
> If done in C, it would be much more lines of code and hardly readable.
>
> Fam
>
--
Best regards. Wang Dong
next prev parent reply other threads:[~2017-05-24 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 2:56 [Qemu-devel] new to qemu with a simple question Wang Dong
2017-05-24 3:11 ` Fam Zheng
2017-05-24 8:37 ` Wang Dong [this message]
2017-05-24 13:30 ` Eric Blake
2017-05-26 4:54 ` Wang Dong
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=d68094a6-574e-9bb7-5574-298285ac477c@linux.vnet.ibm.com \
--to=dongdwdw@linux.vnet.ibm.com \
--cc=famz@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).