From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH 2/4] gdb: remove unused print_command_line and print_command_lines declarations
Date: Tue, 23 Apr 2024 15:22:42 -0400 [thread overview]
Message-ID: <20240423192327.2750109-3-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <20240423192327.2750109-1-simon.marchi@polymtl.ca>
There is no corresponding definition for print_command_line.
There is already a declaration for print_command_lines in
cli/cli-script.h (the implementation is in cli/cli-script.c).
Change-Id: Ic9e67ed04703306d614383ead14e2b2b059b2a8e
---
gdb/gdbcmd.h | 5 -----
1 file changed, 5 deletions(-)
diff --git a/gdb/gdbcmd.h b/gdb/gdbcmd.h
index c212a0caf736..92fa9a7bf14a 100644
--- a/gdb/gdbcmd.h
+++ b/gdb/gdbcmd.h
@@ -29,11 +29,6 @@
#include "cli/cli-script.h"
#include "cli/cli-cmds.h"
-extern void print_command_line (struct command_line *, unsigned int,
- struct ui_file *);
-extern void print_command_lines (struct ui_out *,
- struct command_line *, unsigned int);
-
/* Chains containing all defined "set/show style" subcommands. */
extern struct cmd_list_element *style_set_list;
extern struct cmd_list_element *style_show_list;
--
2.44.0
next prev parent reply other threads:[~2024-04-23 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 19:22 [PATCH 0/4] Remove gdbcmd.h Simon Marchi
2024-04-23 19:22 ` [PATCH 1/4] gdb: move execute function declarations from gdbcmd.h to top.h Simon Marchi
2024-04-23 19:22 ` Simon Marchi [this message]
2024-04-23 19:22 ` [PATCH 3/4] gdb: move style_set_list/style_show_list declarations to cli/cli-style.h Simon Marchi
2024-04-23 19:22 ` [PATCH 4/4] gdb: remove gdbcmd.h Simon Marchi
2024-04-25 13:55 ` [PATCH 0/4] Remove gdbcmd.h Tom Tromey
2024-04-25 17:05 ` Simon Marchi
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=20240423192327.2750109-3-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@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).