From: Yao Qi <qiyaoltc@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: archer@sourceware.org
Subject: Re: C++ draft
Date: Thu, 30 Jun 2011 06:06:00 -0000 [thread overview]
Message-ID: <BANLkTi=r43A6tKmHnK1sF3ya80xBPU+a9edzdN09mGUk8vGf+A@mail.gmail.com> (raw)
In-Reply-To: <m339isxv1s.fsf@fleche.redhat.com>
On Thu, Jun 30, 2011 at 4:05 AM, Tom Tromey <tromey@redhat.com> wrote:
> Yao> In your concrete plan, IIUC, your plan is about converting GDB to C++
> Yao> *partially*, instead of re-write GDB *completely*. Is that
> Yao> correct?
>
> Yes. I don't think a complete rewrite is either practical or advisable.
> Instead I think an incremental approach is best.
>
Tom,
Thanks for your clarification.
I agree.
> Now, one possible criticism is that such incremental changes often peter
> out. And this is definitely a possible problem -- after exceptions and
> python reference counting, what do we care enough about to transform? I
> mean, it is easy to think of areas that can be C++-ified, but are the
> benefits enough to justify the work? Would we be better off just
> writing GCC plugins to check our changes? I tend to think the benefits
> are worth the cost, but it is hard to know this with any certainty.
>
I agree that it is hard to say which part should be first C++-ified,
or C++-ified easily. When the first step (python reference counting
and exception) is done, we may have a clear view of which part should
be C++-ified.
> Yao> I don't think C and C++ co-existance is a problem, or, your plan is
> Yao> about "make good use of C++ to replace some bad and error-prone stuffs
> Yao> in GDB, and keep the rest of GDB as it is". Is it right?
>
> Yes.
That is good to me.
>
> Yao> Just want to know clearly what GDB will be after your plan is performed.
>
> I think we will always have parts in C. At the very least BFD, and if
> you push forward on the gdbserver library project, then the shared bits
> there as well.
Right, that is the reason I ask do we plan to move GDBServer to C++.
This makes sense to me.
--
Yao Qi
next prev parent reply other threads:[~2011-06-30 6:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 21:08 Tom Tromey
2011-06-27 21:23 ` [Archer] " Joel Brobecker
2011-06-29 19:55 ` Tom Tromey
2011-06-29 21:47 ` [Archer] " Joel Brobecker
2011-06-28 4:33 ` Matt Rice
2011-06-28 8:21 ` Yao Qi
2011-06-28 12:21 ` Gary Benson
2011-06-28 17:08 ` Matt Rice
2011-06-28 17:36 ` Jan Kratochvil
2011-06-29 20:08 ` Tom Tromey
2011-06-29 20:06 ` Tom Tromey
2011-06-30 6:06 ` Yao Qi [this message]
2011-09-26 21:01 ` Jim Blandy
2011-06-29 18:52 ` Stan Shebs
2011-06-29 19:03 ` [Archer] " Joel Brobecker
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='BANLkTi=r43A6tKmHnK1sF3ya80xBPU+a9edzdN09mGUk8vGf+A@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=archer@sourceware.org \
--cc=tromey@redhat.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).