From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: phi.debian@gmail.com, gdb@sourceware.org
Subject: Re: Will GDB be rewritten in C++ (again)
Date: Fri, 04 Aug 2017 12:31:00 -0000 [thread overview]
Message-ID: <8360e3y0qc.fsf@gnu.org> (raw)
In-Reply-To: <86d18b3732.fsf@gmail.com> (message from Yao Qi on Fri, 04 Aug 2017 12:28:33 +0100)
> From: Yao Qi <qiyaoltc@gmail.com>
> Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
> Date: Fri, 04 Aug 2017 12:28:33 +0100
>
> Phi Debian <phi.debian@gmail.com> writes:
>
> > Now I retrieved some bandwith and consider going back on GDB dev, but
> > still today I am reluctant with C++
> >
> > So my question is, does this rewrite of GDB in C++ has been shelved or
> > is is still going?
>
> Phi,
> We don't _rewrite_ GDB in C++.
Actually, we do, AFAICT. I've seen many patch series lately whose
main intent is to C++-ify the codebase.
> Most of the code is still written in C, and the code base isn't
> changed dramatically.
That depends on the definition of "dramatically". I think changes are
quite significant.
next prev parent reply other threads:[~2017-08-04 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 14:42 Phi Debian
2017-08-02 14:54 ` Joel Brobecker
2017-08-02 17:08 ` Phi Debian
2017-08-04 11:28 ` Yao Qi
2017-08-04 12:31 ` Eli Zaretskii [this message]
2017-08-05 8:00 ` Phi Debian
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=8360e3y0qc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=phi.debian@gmail.com \
--cc=qiyaoltc@gmail.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