From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Use standard header for offsetof
Date: Fri, 06 Jun 2008 15:32:11 -0500 [thread overview]
Message-ID: <48499ECB.3050105@codemonkey.ws> (raw)
In-Reply-To: <484993AA.2050603@mail.berlios.de>
Stefan Weil wrote:
> Anthony Liguori schrieb:
>> Stefan Weil wrote:
>>> Anthony Liguori schrieb:
>>>>
>>>> I don't understand why you're adding #include <stdef.h> to files
>>>> that do not define offsetof. What's the rationale for that?
>>>>
>>>> Regards,
>>>>
>>>> Anthony Liguori
>>>>
>>> There were several possible ways to replace the defines for offsetof.
>>> After removing the defines, I could
>>>
>>> 1) include stddef.h at the places where offsetof was defined formerly
>>
>> This seems like the most logically thing to do to me. Otherwise,
>> you're unnecessarily increasing the number of #include's in C files.
>>
>
> exec-all.h is one of these places. Adding #include <stddef.h> there
> reduces the number of #include statements
> in C sources, but now all sources which need exec-all.h also include
> stddef.h during compilation.
> So this increases the number of included headers during a compilation.
If you want to take a stab at improving the #include's in QEMU, then you
should do that as a separate patch. I'll warn you though that I doubt
there's a lot of people interested in that and I think there's always
reservations about changing headers because it often causes subtle
breakages.
Don't complicate what should be a simple patch to use the standard
offset of though with other clean-ups.
Regards,
Anthony Liguori
prev parent reply other threads:[~2008-06-06 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 17:37 [Qemu-devel] [PATCH] Use standard header for offsetof Stefan Weil
2008-06-02 6:21 ` Johannes Schindelin
2008-06-03 19:08 ` Anthony Liguori
2008-06-03 21:03 ` Stefan Weil
2008-06-03 21:24 ` Anthony Liguori
2008-06-06 19:44 ` Stefan Weil
2008-06-06 19:58 ` Andreas Färber
2008-06-09 10:30 ` Ian Jackson
2008-06-06 20:32 ` 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=48499ECB.3050105@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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.