From: Mike Frysinger <vapier@gentoo.org>
To: Pedro Alves <palves@redhat.com>,
Ashutosh <ashutoshpal2006@gmail.com>,
Duane Ellis <duane@duaneellis.com>,
Klaus Rudolph <lts-rudolph@gmx.de>,
gdb@sourceware.org
Subject: Re: Using C++ code inside gdb
Date: Sun, 11 Oct 2015 08:57:00 -0000 [thread overview]
Message-ID: <20151011085715.GE4119@vapier.lan> (raw)
In-Reply-To: <20151010213205.GB4119@vapier.lan>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
On 10 Oct 2015 17:32, Mike Frysinger wrote:
> On 09 Oct 2015 10:41, Pedro Alves wrote:
> > On 10/09/2015 07:08 AM, Ashutosh wrote:
> > > Regarding using C++, I just hit upon the following conversation on the
> > > gdb-patches list:
> > > https://sourceware.org/ml/gdb-patches/2015-02/msg00202.html
> > >
> > > where it seems that there's some work going on compiling gdb sources
> > > with g++. Any idea if this support is available in some form already
> > > in gdb 7.10 or when is it planned to be released?
> >
> > The status in the wiki page linked from that url is accurate.
> >
> > GDB nowadays builds and links in C++ when configured
> > with --enable-build-with-cxx, though that still spews a ton of warnings.
> > There's been constant incremental progress so we'll get there eventually.
> >
> > No release has been marked as the one where we'll switch to C++ as
> > default language -- it'll get done when it's done; though the sooner
> > the better. :-)
>
> even if the C++ frontend is used, and C++ is the default language, that doesn't
> mean that all C++ functionality will be accepted. there are a lot of design
> patterns and C++ APIs that are generally bad, and gdb is meant to be portable.
> so i'd expect there will be guidelines put together as to acceptable standards
> base (C11/C14/etc...) as well as headers and interfaces that are permitted and
> ones that are banned.
seems like gcc has already done this:
https://gcc.gnu.org/codingconventions.html
probably be best to try and follow that, or at least use it as a base.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-11 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 10:57 Ashutosh
2015-10-08 13:05 ` Aw: " Klaus Rudolph
2015-10-09 3:20 ` Ashutosh
2015-10-09 4:29 ` Duane Ellis
2015-10-09 6:08 ` Ashutosh
2015-10-09 9:41 ` Pedro Alves
2015-10-09 10:00 ` vijay nag
2015-10-09 10:06 ` Pedro Alves
2015-10-10 21:32 ` Mike Frysinger
2015-10-11 8:57 ` Mike Frysinger [this message]
2015-10-11 14:23 ` 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=20151011085715.GE4119@vapier.lan \
--to=vapier@gentoo.org \
--cc=ashutoshpal2006@gmail.com \
--cc=duane@duaneellis.com \
--cc=gdb@sourceware.org \
--cc=lts-rudolph@gmx.de \
--cc=palves@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