From: Pedro Alves <palves@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: C++11 (abridged version)
Date: Thu, 27 Oct 2016 19:24:00 -0000 [thread overview]
Message-ID: <a5d6f9c4-78aa-4429-dc5a-e0a6c5e24a8a@redhat.com> (raw)
In-Reply-To: <4300d24a-8711-c5de-79ce-7c530162288c@redhat.com>
On 10/20/2016 06:07 PM, Pedro Alves wrote:
> My opinion on #3 (should we require C++11 now), is yes. C++11 is a
> great step up from C++03, and being able to use it fully would result
> in a more efficiency gdb, and would also allow simplifying things that
> require ugly workarounds in C++03. I.e., if you hate C++ and you think
> it's messy, it may actually be that what you hate is C++03, and that you'd
> actually like C++11 if you give it a chance. E.g., rvalue references, efficient
> move-aware containers (also allowing us to make containers "own" the containing
> objects, resulting in even simpler code), template aliases, variadic templates,
> etc. etc. C++11 would avoid having to consider reimplementing basic utilities
> like e.g., a type-safe hash table. C++11 is also a _simpler_ language in a way,
> as some ugly warts have been ironed out in the language (e.g., std::string
> and contiguous buffer guarantees).
Seems like pretty much everyone is in agreement with this, so
I've sent a new patch set for this now:
https://sourceware.org/ml/gdb-patches/2016-10/msg00773.html
I'd appreciate a review.
Thanks,
Pedro Alves
prev parent reply other threads:[~2016-10-27 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 17:08 Pedro Alves
2016-10-20 18:10 ` Luis Machado
2016-10-20 18:24 ` Tom Tromey
2016-10-20 19:05 ` Eli Zaretskii
2016-10-20 19:09 ` Pedro Alves
2016-10-20 19:41 ` Pedro Alves
2016-10-20 19:57 ` Eli Zaretskii
2016-10-28 17:26 ` Pedro Alves
2016-10-20 19:41 ` Eli Zaretskii
2016-10-20 19:38 ` Yao Qi
2016-10-20 19:45 ` Pedro Alves
2016-10-25 20:29 ` Keith Seitz
2016-10-26 0:41 ` Pedro Alves
2016-10-27 0:04 ` Kevin Buettner
2016-10-27 19:24 ` Pedro Alves [this message]
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=a5d6f9c4-78aa-4429-dc5a-e0a6c5e24a8a@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@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