From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: Alan Hayward <Alan.Hayward@arm.com>,
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, 29 Jan 2018 16:54:00 -0000 [thread overview]
Message-ID: <CAH=s-PM4_JMM+-uctVGtj7t-+08HH-Af-qD_7f5TY1aeyVEWaw@mail.gmail.com> (raw)
In-Reply-To: <edb69de1-bbbe-bf9f-78c9-c07237338d3c@ericsson.com>
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 :)
--
Yao (齐尧)
next prev parent reply other threads:[~2018-01-29 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a06ab31b-0144-82fe-5d29-4e81016990d3@arm.com>
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 [this message]
2018-01-30 15:16 ` Alan Hayward
2018-02-05 16:21 ` 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='CAH=s-PM4_JMM+-uctVGtj7t-+08HH-Af-qD_7f5TY1aeyVEWaw@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=prudo@linux.vnet.ibm.com \
--cc=simark@simark.ca \
--cc=simon.marchi@ericsson.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