From: Stan Shebs <stanshebs@earthlink.net>
To: archer@sourceware.org
Subject: Re: C++ draft
Date: Wed, 29 Jun 2011 18:52:00 -0000 [thread overview]
Message-ID: <4E0B7462.8020004@earthlink.net> (raw)
In-Reply-To: <m3tybb7zjz.fsf@fleche.redhat.com>
On 6/27/11 2:08 PM, Tom Tromey wrote:
> I've been working on another proposal to move gdb to C++. I'd
> appreciate help with it. Here is what I have so far.
Looks good to me! At some point there should be a task to define the
accepted set of C++ features; I really really want to avoid people
having to spend time debating minutiae of the language, and I don't want
to hear about how target vectors could be recoded using
amazing-but-not-yet-implemented features of C++2x. :-)
Stan
next prev parent reply other threads:[~2011-06-29 18:52 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
2011-09-26 21:01 ` Jim Blandy
2011-06-29 18:52 ` Stan Shebs [this message]
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=4E0B7462.8020004@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=archer@sourceware.org \
/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).