All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Eduardo Habkost <eduardo@habkost.net>,
	qemu-devel@nongnu.org
Cc: Zhao Liu <zhao1.liu@intel.com>
Subject: [Question] What is the definition of “private” fields in QOM?
Date: Sun, 20 Oct 2024 00:10:14 +0800	[thread overview]
Message-ID: <ZxPZ5oUDRcVroh7o@intel.com> (raw)

Hi maintainers and list,

In the QOM structure, the class and object structs have two members:
parent_class and parent_obj, which are often marked as "< private >" in
the comment.

I couldn’t find information on why to define ‘private’ and ‘public’,
even in the earliest QOM commits and the patch emails I could find.

Does ‘private’ refer to the internal implementation code of QOM, or does
it refer to the specific code that defines and implements this object
and its class?

I understand the original idea of private field indicates it cannot be
accessed directly out of the "private" scope.

Regards,
Zhao



             reply	other threads:[~2024-10-19 15:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 16:10 Zhao Liu [this message]
2024-10-21  8:35 ` [Question] What is the definition of “private” fields in QOM? Daniel P. Berrangé
2024-10-21  9:22   ` Zhao Liu
2024-10-21  9:25 ` Peter Maydell
2024-10-21 14:22   ` Zhao Liu
2024-10-21 14:20     ` Peter Maydell
2024-10-21 15:18       ` Zhao Liu
2024-10-21 15:06         ` Peter Maydell
2024-10-21 15:41           ` Zhao Liu
2024-10-21 16:47             ` Peter Maydell
2024-10-22  3:08               ` Junjie Mao
2024-10-22  8:42                 ` Peter Maydell
2024-10-22 15:09                   ` Zhao Liu
2024-10-22 15:01               ` Zhao Liu
2024-10-21 18:46   ` BALATON Zoltan

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=ZxPZ5oUDRcVroh7o@intel.com \
    --to=zhao1.liu@intel.com \
    --cc=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=pbonzini@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.