From: Yao Qi <qiyaoltc@gmail.com>
To: Phi Debian <phi.debian@gmail.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Will GDB be rewritten in C++ (again)
Date: Fri, 04 Aug 2017 11:28:00 -0000 [thread overview]
Message-ID: <86d18b3732.fsf@gmail.com> (raw)
In-Reply-To: <CAJOr74iEEjW-eOtPT7OnpKZMmi4b2eJjEvPkozTmFao804EaGw@mail.gmail.com> (Phi Debian's message of "Wed, 2 Aug 2017 16:42:05 +0200")
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++. As Joel said, GDB requires a C++11
compiler, because we started to use some C++-11 features. Most of the
code is still written in C, and the code base isn't changed dramatically.
>
> For what I see on my distro, the gdb-7.11.1 is still C, so i would
> guess that no progress has been done since 2012 ?
>
> PS: Don't flame on C++ vs C, my question is really about the road map
> of GDB. If this is pure C I could refresh my mem to contribute, if
> going C++ this is fine too, I would simply find other project there
> are plenty :)
One of the reasons that we move GDB to C++ is to make maintenance and
development easier, not harder. You should feel easier to write code in
GDB nowadays.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-08-04 11:28 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 [this message]
2017-08-04 12:31 ` Eli Zaretskii
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=86d18b3732.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb@sourceware.org \
--cc=phi.debian@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