From: Avi Kivity <avi@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aliguori@us.ibm.com, filip.navara@gmail.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/3] Introduce qobject header file
Date: Thu, 06 Aug 2009 17:02:48 +0300 [thread overview]
Message-ID: <4A7AE288.1020905@redhat.com> (raw)
In-Reply-To: <1249566736-5020-2-git-send-email-lcapitulino@redhat.com>
On 08/06/2009 04:52 PM, Luiz Capitulino wrote:
> This file contains basic definitions for the QEMU Object Model,
> all object implementions must include this file and add its
> type code in qtype_t enum.
>
>
> +
> +typedef enum {
> + QTYPE_NONE,
> +} qtype_t;
> +
> +struct QObject;
> +
> +typedef struct QType {
> + qtype_t code;
>
Is this really needed? You can check if an object is a particular type
by checking its ->type agains whatever you're interested in. Of course
you should refrain from doing so unless there's no choice.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-06 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 13:52 [Qemu-devel] [PATCH RFC 0/3] QEMU Object Model Luiz Capitulino
2009-08-06 13:52 ` [Qemu-devel] [PATCH 1/3] Introduce qobject header file Luiz Capitulino
2009-08-06 14:02 ` Avi Kivity [this message]
2009-08-06 14:07 ` [Qemu-devel] " Luiz Capitulino
2009-08-06 15:54 ` [Qemu-devel] " malc
2009-08-06 13:52 ` [Qemu-devel] [PATCH 2/3] Introduce QString data type Luiz Capitulino
2009-08-06 13:52 ` [Qemu-devel] [PATCH 3/3] Introduce QNumber " Luiz Capitulino
2009-08-06 14:04 ` [Qemu-devel] " Avi Kivity
2009-08-06 14:05 ` François Revol
2009-08-06 14:48 ` Avi Kivity
2009-08-06 14:10 ` Luiz Capitulino
2009-08-06 21:21 ` Luiz Capitulino
2009-08-06 14:06 ` [Qemu-devel] Re: [PATCH RFC 0/3] QEMU Object Model Avi Kivity
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=4A7AE288.1020905@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=filip.navara@gmail.com \
--cc=lcapitulino@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 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.