From: Richard Yang <weiyang@linux.vnet.ibm.com>
To: Dmitry Zamaruev <dmitry.zamaruev@gmail.com>
Cc: Richard Yang <weiyang@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Why QEMUClock is defined in qemu-timer.c?
Date: Wed, 1 Feb 2012 09:33:45 +0800 [thread overview]
Message-ID: <20120201013345.GA3929@richard> (raw)
In-Reply-To: <CAGvhtCDut5czJZXC6Sm4LnDFU3k3dsQ9Ysti7L1hm46vA1OK9g@mail.gmail.com>
On Tue, Jan 31, 2012 at 12:00:30PM +0200, Dmitry Zamaruev wrote:
>This is used in many places.
>Maybe to simulate 'private' variables and access methods like in C++.
>
>If you define structure in .c file then every function that works with
>this structure must reside in same file. And any other code to use
>structure must use access-functions (api) to alter it and not directly
>(compiler will issue error about incomplete type).
>This way you could change structure or internal data handling without
>affecting external code that relies on "stable api functions".
Thanks for your explanation.
I learned a lot.
--
Richard Yang
Help you, Help me
prev parent reply other threads:[~2012-02-01 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 5:55 [Qemu-devel] Why QEMUClock is defined in qemu-timer.c? Richard Yang
2012-01-31 6:12 ` Mulyadi Santosa
2012-01-31 6:35 ` Richard Yang
2012-01-31 10:00 ` Dmitry Zamaruev
2012-02-01 1:33 ` Richard Yang [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=20120201013345.GA3929@richard \
--to=weiyang@linux.vnet.ibm.com \
--cc=dmitry.zamaruev@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).