Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: C++11 (abridged version)
Date: Thu, 20 Oct 2016 19:45:00 -0000	[thread overview]
Message-ID: <9bee3c7f-092b-68ec-fd3f-093ae0b03365@redhat.com> (raw)
In-Reply-To: <CAH=s-PPma78qTWryjSFa2KByV5JRosM2VRSmbxtSmW7hBNshrA@mail.gmail.com>

On 10/20/2016 08:37 PM, Yao Qi wrote:
> Hi Pedro,
> I kept silence on the discussion in the past several weeks, because
> I don't know much on C++.  I can't think of any reason we should
> block C++ 11 transition.  I've got "C++ Primer, fifth edition" on my
> desk.  It covers C++ 11 :)
> 
> It is a right thing to move to C++ 11.  However, we need to think
> about the priority of each work.  We still have bugs to fix, new features
> to add, patches to review.  They are very important in the short term,
> next release, for example.  We can't afford several months doing code
> conversion without any real development and bug fixes.  Code
> conversion should be a background task, running along with development
> and bug fixes for some years.

Definitely agreed.  Myself I've been spending more time on it
than I can really afford.  My idea in the past weeks was to
plant the seed for others to come in and help (e.g., the
std::string patches and the gdb::unique_ptr patches).  I had
no idea getting that done would take this long...

Thanks,
Pedro Alves


  reply	other threads:[~2016-10-20 19:45 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 [this message]
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

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=9bee3c7f-092b-68ec-fd3f-093ae0b03365@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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