From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: C++11 (abridged version)
Date: Thu, 20 Oct 2016 19:05:00 -0000 [thread overview]
Message-ID: <83d1iuu9i0.fsf@gnu.org> (raw)
In-Reply-To: <4300d24a-8711-c5de-79ce-7c530162288c@redhat.com> (message from Pedro Alves on Thu, 20 Oct 2016 18:07:58 +0100)
> From: Pedro Alves <palves@redhat.com>
> Date: Thu, 20 Oct 2016 18:07:58 +0100
>
> On #4 (policy for newer standard versions), as I've been saying many
> times in the past week, I think that what matters is whether there's
> reasonably widespread compiler availability, meaning the latest stable
> releases of distributions include a compiler for the standard, or it's
> easy to get one by installing some optional package. If reasonably
> available, then we should switch, and take advantage of the great work
> our compiler and standards friends have been doing.
IMO, this is too vague for a policy. I proposed a much more
quantitative criterion, one that doesn't run the risk of triggering
long disputes with no clear-cut ways of making a decision. I'm okay
with other criteria, as long as they are clear, easily applied, and
don't require subjective interpretation.
My opinion on other items was already voiced here.
next prev parent reply other threads:[~2016-10-20 19:05 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 [this message]
2016-10-20 19:09 ` Pedro Alves
2016-10-20 19:41 ` Eli Zaretskii
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: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=83d1iuu9i0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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