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] Don't declare cli_set_logging
Date: Thu, 23 Jun 2022 20:27:23 +0000 (GMT)	[thread overview]
Message-ID: <20220623202723.A8B633854161@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d75bdf170e6eadff038d4265de99b7103241f1ef

commit d75bdf170e6eadff038d4265de99b7103241f1ef
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Jun 23 14:26:13 2022 -0600

    Don't declare cli_set_logging
    
    cli_set_logging is declared but not defined.  It's probably a leftover
    from whenever interpreters were changed to use inheritance.  This
    patch removes the declaration.  Tested by grep and rebuilding.

Diff:
---
 gdb/cli/cli-interp.h | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/gdb/cli/cli-interp.h b/gdb/cli/cli-interp.h
index 2e89a36d86a..863e8c3133e 100644
--- a/gdb/cli/cli-interp.h
+++ b/gdb/cli/cli-interp.h
@@ -34,11 +34,6 @@ public:
   bool supports_command_editing () override;
 };
 
-/* The CLI interpreter's set_logging_proc method.  Exported so other
-   interpreters can reuse it.  */
-extern void cli_set_logging (struct interp *interp,
-			     ui_file_up logfile, bool logging_redirect);
-
 extern int cli_interpreter_supports_command_editing (struct interp *interp);
 
 extern void cli_interpreter_pre_command_loop (struct interp *self);


                 reply	other threads:[~2022-06-23 20: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:
  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=20220623202723.A8B633854161@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: 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).