Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>,
	 GDB Patches <gdb-patches@sourceware.org>
Subject: Re: C++11 (abridged version)
Date: Thu, 20 Oct 2016 18:24:00 -0000	[thread overview]
Message-ID: <87eg3azxog.fsf@tromey.com> (raw)
In-Reply-To: <e059f0c8-3545-e977-4354-8b7e58de1915@codesourcery.com> (Luis	Machado's message of "Thu, 20 Oct 2016 13:10:26 -0500")

>>>>> "Luis" == Luis Machado <lgustavo@codesourcery.com> writes:

Luis> It would be great if people manifesting their opinions offlist would
Luis> do so through the list. After all, this is an upstream project and
Luis> opinions from everyone are appreciated. Otherwise it feels like you
Luis> are making this decision based on your own opinion of the matter. We
Luis> never saw any of the several people that got in touch with you
Luis> directly. :-)

I try to limit my exposure to the list.

C++11 is a major improvement.  There are already existing patches that
it simplifies.  So I am in favor it; however I think a valid reason to
defer the transition would be if there is an active user base for whom
it would be unduly difficult to upgrade.  There are some weasel words in
there because I think some judgment must be involved.

Luis> As long as we have a sane codebase that makes contributions easier for
Luis> everyone (instead of getting in the way with cryptic smarts and
Luis> trickery simply to reduce code size), it should be good. Compilers are
Luis> doing a better job these days anyway, and making code as compact as
Luis> possible, though pleasing in some nerdy way, may not yield real
Luis> benefit in the end. It may actually be harder to follow.

I think the cases in question aren't of the form "shorter code is more
pleasing" but of the form "move the maintenance burden to the C++
library".  The former is aesthetic, but the latter means less work
locally.

Tom


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

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=87eg3azxog.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --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