From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [RfC PATCH 0/2] qdev: property macros.
Date: Tue, 28 Jul 2009 18:21:58 +0200 [thread overview]
Message-ID: <1248798120-1083-1-git-send-email-kraxel@redhat.com> (raw)
Hi folks,
Presenting a new version of my patch to continue the discussion how
the macros should look like ;)
There are DEFINE_PROP_$TYPE("name", struct, field, default) macros for
each property type, thus no gcc-powered automagic selection.
typeof(struct->field) is verifyed to be the correct one for the given
property though (new in this version). This uses gcc extentions, but
as it is a check only it could easily be turned off for non-gcc
compilers if needed.
Comments?
cheers,
Gerd
next reply other threads:[~2009-07-28 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 16:21 Gerd Hoffmann [this message]
2009-07-28 16:21 ` [Qemu-devel] [RfC PATCH 1/2] qdev/pci: make PCIDevice->devfn uint32_t Gerd Hoffmann
2009-07-28 16:22 ` [Qemu-devel] [RfC PATCH 2/2] qdev/prop: macros for creating typechecked properties Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 10:24 [Qemu-devel] [RfC PATCH 0/2] qdev: property macros Gerd Hoffmann
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=1248798120-1083-1-git-send-email-kraxel@redhat.com \
--to=kraxel@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).