From: Simon Marchi <simon.marchi@ericsson.com>
To: Alan Hayward <Alan.Hayward@arm.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: Philipp Rudo <prudo@linux.vnet.ibm.com>,
Simon Marchi <simark@simark.ca>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH] Use visitors for make_gdb_type
Date: Mon, 05 Feb 2018 16:21:00 -0000 [thread overview]
Message-ID: <c3155a59-d9b5-2844-52ed-36266e9455a4@ericsson.com> (raw)
In-Reply-To: <0D465C5F-EA4D-4A6C-94C7-9EE3377CAE7E@arm.com>
On 2018-01-30 10:15 AM, Alan Hayward wrote:
>
>
>> On 29 Jan 2018, at 16:54, Yao Qi <qiyaoltc@gmail.com> wrote:
>>
>> On Mon, Jan 29, 2018 at 4:12 PM, Simon Marchi <simon.marchi@ericsson.com> wrote:
>>>
>>> That seems like unnecessary boilerplate to me. I really don't see why classes derived
>>> from tdesc_element_visitor have to implement methods for nodes they don't care about.
>>>
>>> I added Yao in CC so he can chime in.
>>
>> When I wrote tdesc_element_visitor, in my mind, it is an interface, so
>> I expect child
>> class implement all the methods, because at that moment, all methods are needed,
>> no empty methods. However, the situation changed a little bit, as per
>> Alan's needs,
>> part of the methods of tdesc_element_visitor are needed, and the rest of methods
>> are empty somewhere. I don't mind converting tdesc_element_visitor into a base
>> class which has all these methods empty as a default. That is fine to
>> me. By the
>> way, Alan's approach is fine to me as well :)
>>
>
> Iâve removed the extra class and replaced with default implementations in
> tdesc_element_visitor.
>
> All ok?
>
>
> Tested on a make check on x86 targets=all build with target board unix native-gdbserver.
> Built for power (because it does not use new target descriptions), but am unable to test.
Hi Alan,
This version LGTM.
Thanks,
Simon
prev parent reply other threads:[~2018-02-05 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 15:14 Alan Hayward
2018-01-26 15:30 ` Alan Hayward
2018-01-29 2:24 ` Simon Marchi
2018-01-29 9:30 ` Philipp Rudo
2018-01-29 15:31 ` Alan Hayward
2018-01-29 16:13 ` Simon Marchi
2018-01-29 16:54 ` Yao Qi
2018-01-30 15:16 ` Alan Hayward
2018-02-05 16:21 ` Simon Marchi [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=c3155a59-d9b5-2844-52ed-36266e9455a4@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=prudo@linux.vnet.ibm.com \
--cc=qiyaoltc@gmail.com \
--cc=simark@simark.ca \
/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).