public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
Cc: Tom Tromey <>
Subject: [pushed] Remove value_next declaration
Date: Mon, 30 Jan 2023 16:27:02 -0700	[thread overview]
Message-ID: <> (raw)

value_next is declared but not defined.  It's long obsolete.  This
patch removes the stray declaration.
 gdb/value.h | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/gdb/value.h b/gdb/value.h
index 1e80b74b41f..f022510ded1 100644
--- a/gdb/value.h
+++ b/gdb/value.h
@@ -119,13 +119,6 @@ struct value_ref_policy
 typedef gdb::ref_ptr<struct value, value_ref_policy> value_ref_ptr;
-/* Values are stored in a chain, so that they can be deleted easily
-   over calls to the inferior.  Values assigned to internal variables,
-   put into the value history or exposed to Python are taken off this
-   list.  */
-struct value *value_next (const struct value *);
 /* Type of the value.  */
 extern struct type *value_type (const struct value *);

                 reply	other threads:[~2023-01-30 23:27 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).