aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/python.c
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2025-05-22 11:54:16 -0600
committerTom Tromey <tromey@adacore.com>2025-06-26 06:15:59 -0600
commit5fe70629ceafc157d896adec7799a8888d51dd6b (patch)
treed256c85b7b1dd9961bde24979bd9148a262c16f1 /gdb/python/python.c
parentcdf176bebcf2466b1e921d0e50e405b6e5994208 (diff)
downloadbinutils-5fe70629ceafc157d896adec7799a8888d51dd6b.zip
binutils-5fe70629ceafc157d896adec7799a8888d51dd6b.tar.gz
binutils-5fe70629ceafc157d896adec7799a8888d51dd6b.tar.bz2
Change file initialization to use INIT_GDB_FILE macro
This patch introduces a new macro, INIT_GDB_FILE. This is used to replace the current "_initialize_" idiom when introducing a per-file initialization function. That is, rather than write: void _initialize_something (); void _initialize_something () { ... } ... now you would write: INIT_GDB_FILE (something) { ... } The macro handles both the declaration and definition of the function. The point of this approach is that it makes it harder to accidentally cause an initializer to be omitted; see commit 2711e475 ("Ensure cooked_index_entry self-tests are run"). Specifically, the regexp now used by make-init-c seems harder to trick. New in v2: un-did some erroneous changes made by the script. The bulk of this patch was written by script. Regression tested on x86-64 Fedora 41.
Diffstat (limited to 'gdb/python/python.c')
-rw-r--r--gdb/python/python.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/gdb/python/python.c b/gdb/python/python.c
index ff50c42..cb0d642 100644
--- a/gdb/python/python.c
+++ b/gdb/python/python.c
@@ -2717,9 +2717,7 @@ test_python ()
/* See python.h. */
cmd_list_element *python_cmd_element = nullptr;
-void _initialize_python ();
-void
-_initialize_python ()
+INIT_GDB_FILE (python)
{
cmd_list_element *python_interactive_cmd
= add_com ("python-interactive", class_obscure,