From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 1/2] gdb: add type::name / type::set_name
Date: Sat, 16 May 2020 09:58:35 -0600 [thread overview]
Message-ID: <87blmn7txw.fsf@tromey.com> (raw)
In-Reply-To: <20200514181812.25795-1-simon.marchi@efficios.com> (Simon Marchi via Gdb-patches's message of "Thu, 14 May 2020 14:18:11 -0400")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> Add the `name` and `set_name` methods on `struct type`, in order to
Simon> remove the `TYPE_NAME` macro. In this patch, the `TYPE_NAME` macro is
Simon> changed to use `type::name`, so all the call sites that are used to set
Simon> the type name are changed to use `type::set_name`. The next patch will
Simon> remove `TYPE_NAME` completely.
Looks good, thanks.
Tom
prev parent reply other threads:[~2020-05-16 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 18:18 Simon Marchi
2020-05-14 18:18 ` [PATCH 2/2] gdb: remove TYPE_NAME macro Simon Marchi
2020-05-16 16:00 ` Tom Tromey
2020-05-16 16:35 ` Simon Marchi
2020-05-16 18:18 ` Tom Tromey
2020-05-16 19:10 ` Simon Marchi
2020-05-16 19:26 ` Tom Tromey
2020-05-16 19:33 ` Simon Marchi
2020-05-16 15:58 ` Tom Tromey [this message]
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=87blmn7txw.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