public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Make struct value data members private Date: Mon, 13 Feb 2023 22:31:07 +0000 (GMT) [thread overview] Message-ID: <20230213223107.A77B33858416@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8f4135314ae6e1a98a36295c85af5b246dfa00ff commit 8f4135314ae6e1a98a36295c85af5b246dfa00ff Author: Tom Tromey <tom@tromey.com> Date: Wed Feb 1 08:25:40 2023 -0700 Make struct value data members private This hoists the 'private' in struct value to also encompass the data members. Approved-By: Simon Marchi <simon.marchi@efficios.com> Diff: --- gdb/value.h | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/gdb/value.h b/gdb/value.h index 225a3c851c4..7708530ddcc 100644 --- a/gdb/value.h +++ b/gdb/value.h @@ -609,6 +609,8 @@ public: in the history. The value is removed from the value chain. */ int record_latest (); +private: + /* Type of value; either not an lval, or one of the various different possible kinds of lval. */ enum lval_type m_lval = not_lval; @@ -785,8 +787,6 @@ public: loaded from the inferior. */ ULONGEST m_limited_length = 0; -private: - /* Allocate a value and its contents for type TYPE. If CHECK_SIZE is true, then apply the usual max-value-size checks. */ static struct value *allocate (struct type *type, bool check_size); @@ -806,15 +806,11 @@ private: return failure here, which will ultimately throw an error. */ bool set_limited_array_length (); -public: /* Temporary */ - /* Allocate the contents of this value if it has not been allocated yet. If CHECK_SIZE is true, then apply the usual max-value-size checks. */ void allocate_contents (bool check_size); -private: - /* Helper function for value_contents_eq. The only difference is that this function is bit rather than byte based.
reply other threads:[~2023-02-13 22:31 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230213223107.A77B33858416@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).