From: Anthony Liguori <aliguori@us.ibm.com>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Avi Kivity <avi@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] QEMU Object Model
Date: Thu, 21 Jul 2011 10:46:23 -0500 [thread overview]
Message-ID: <4E2849CF.7070800@us.ibm.com> (raw)
In-Reply-To: <CAKPcRGr9_SzP8GEBjP3N909ypaZgfPVN7kQzvSZirw__S4KRyA@mail.gmail.com>
On 07/21/2011 10:19 AM, Luca Tettamanti wrote:
> On Thu, Jul 21, 2011 at 4:49 PM, Anthony Liguori<aliguori@us.ibm.com> wrote:
> [cut]
>> And it's really not that much nicer than the C version. The problem with
>> C++ is that even though the type system is much, much nicer, it still
>> doesn't have introspection or decorators. These two things would be the
>> killer feature for doing the sort of things we need to do and is really
>> where most of the ugliness comes from.
>
> QT has introspection; what about using the core (i.e. QObject and moc)
> to build QEMU object model?
I don't know QT very well except that it's a very odd subset of C++ and
custom extensions implemented by a preprocessor.
Regards,
Anthony Liguori
>
> L
>
prev parent reply other threads:[~2011-07-21 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 15:14 [Qemu-devel] [RFC] QEMU Object Model Anthony Liguori
[not found] ` <4E2824D2.2050401@redhat.com>
[not found] ` <4E2827A2.6010603@us.ibm.com>
[not found] ` <4E282BE3.1050404@redhat.com>
2011-07-21 14:49 ` Anthony Liguori
2011-07-21 15:04 ` Avi Kivity
2011-07-21 15:45 ` Anthony Liguori
2011-07-21 15:57 ` Avi Kivity
2011-07-21 16:32 ` Anthony Liguori
2011-07-22 7:46 ` Kevin Wolf
2011-07-22 12:40 ` Anthony Liguori
2011-07-22 13:15 ` Kevin Wolf
2011-07-22 13:52 ` Anthony Liguori
2011-07-21 15:19 ` Luca Tettamanti
2011-07-21 15:32 ` Avi Kivity
2011-07-21 15:46 ` Anthony Liguori [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=4E2849CF.7070800@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=kronos.it@gmail.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).