From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: remove SYMBOL_*_OPS macros
Date: Fri, 19 Jan 2024 10:06:36 -0700 [thread overview]
Message-ID: <87o7dhl0bn.fsf@tromey.com> (raw)
In-Reply-To: <20240119163148.70597-1-simon.marchi@efficios.com> (Simon Marchi's message of "Fri, 19 Jan 2024 11:31:47 -0500")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
Simon> Remove SYMBOL_BLOCK_OPS, SYMBOL_COMPUTED_OPS and SYMBOL_REGISTER_OPS, in
Simon> favor of methods on struct symbol. More changes could be done here to
Simon> improve the design and make things safer, but I just wanted to do a
Simon> straightforward change to remove the macros for now.
Thanks.
Simon> + if (auto computed_ops = var->computed_ops ())
Simon> + return computed_ops->read_variable (var, frame);
This one spot uses auto, but no other change does.
That seemed weird. Normally I wouldn't mention it but I also noticed:
Simon> + if (framefunc != nullptr)
Simon> + {
Looks like the wrong indentation here.
Tom
next prev parent reply other threads:[~2024-01-19 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 16:31 Simon Marchi
2024-01-19 17:06 ` Tom Tromey [this message]
2024-01-19 20:30 ` 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=87o7dhl0bn.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).