From: Tom Tromey <tom@tromey.com>
To: "Ali Tamur via gdb-patches" <gdb-patches@sourceware.org>
Cc: Ali Tamur <tamur@google.com>
Subject: Re: [PATCH] Disambiguate info_print_options
Date: Sun, 26 Jan 2020 16:15:00 -0000 [thread overview]
Message-ID: <87a76a6vwn.fsf@tromey.com> (raw)
In-Reply-To: <20200125050825.53004-1-tamur@google.com> (Ali Tamur via gdb-patches's message of "Fri, 24 Jan 2020 21:08:25 -0800")
>>>>> "Ali" == Ali Tamur via gdb-patches <gdb-patches@sourceware.org> writes:
Ali> struct info_print_options is defined in both symtab.c and stack.c, which is
Ali> an ODR violation. So, I am renaming one of them. (Please suggest a better
Ali> name, what I picked is not good).
Thank you for doing this.
I tend to think the naming of these "throwaway" structures isn't very
important.
That said, the comment just above reads:
/* Structure to hold the values of the options used by the 'info variables'
and 'info functions' commands. These correspond to the -q, -t, and -n
options. */
So how about "info_vars_funcs_options"?
Maybe make_info_sources_options_def_group should be renamed as well.
And perhaps info_print_command_completer. My thinking here is that it
is best if the related names are all consistent.
thanks,
Tom
next prev parent reply other threads:[~2020-01-26 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 7:38 Ali Tamur via gdb-patches
2020-01-26 16:15 ` Tom Tromey [this message]
2020-01-28 10:14 ` Ali Tamur via gdb-patches
2020-02-01 23:22 ` Ali Tamur via gdb-patches
2020-02-05 21:40 ` Ali Tamur via gdb-patches
2020-02-05 21:49 ` 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=87a76a6vwn.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tamur@google.com \
/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