From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: markus.t.metzger@intel.com, brobecker@adacore.com,
gdb-patches@sourceware.org, jan.kratochvil@redhat.com,
simon.marchi@ericsson.com
Subject: Re: [PATCH 1/3] Introduce gdb::unique_ptr
Date: Thu, 13 Oct 2016 12:12:00 -0000 [thread overview]
Message-ID: <32e74745-a5d6-e6b9-b699-d303580f2c92@redhat.com> (raw)
In-Reply-To: <834m4hbxlz.fsf@gnu.org>
On 10/12/2016 12:44 PM, Eli Zaretskii wrote:
>> Cc: markus.t.metzger@intel.com, brobecker@adacore.com,
>> gdb-patches@sourceware.org, jan.kratochvil@redhat.com,
>> simon.marchi@ericsson.com
>> From: Pedro Alves <palves@redhat.com>
>> Date: Wed, 12 Oct 2016 12:25:21 +0100
>>
>> On 10/12/2016 12:04 PM, Eli Zaretskii wrote:
>>>> Cc: brobecker@adacore.com, gdb-patches@sourceware.org,
>>>> jan.kratochvil@redhat.com, simon.marchi@ericsson.com
>>>> From: Pedro Alves <palves@redhat.com>
>>>> Date: Wed, 12 Oct 2016 11:11:50 +0100
>>>>
>>>>> . Should we start using C++11 features in GDB?
>>>>
>>>> I would hope that no one would suggest that we shouldn't use
>>>> C++11 features just because they like C++03 better than C++11.
>>>> That would make no sense.
>>>
>>> It would make perfect sense if we decide to require a version of GCC
>>> older than 4.8.1 as a prerequisite for building GDB.
>>
>> I can't see how that is a reply to what I said. I said _liking_ C++11
>> better over C++03. As in: "I'm just not going to use
>> C++11 features, because I hate C++11, but C++03 is perfectly
>> fine".
>
> That's a no-brainer,
Good that you agree.
> but if that was the only thing you were saying,
That was not the only thing I was saying... That was preamble
for the next paragraph:
"In my mind, the only reason you'd not use C++11 over C++03
is simply because you couldn't because you don't have a ..."
It seems like we keep talking past each other.
> That decision
> has IMO very little to do with whether we like C++03 more or not,
> because if we go by that criterion alone, we should take Jan's
> suggestion and switch to the latest version as soon as it is released,
> right?
Right. By that criteria, I'd switch to C++17 in a heart beat.
C++17 can make C++ code look significantly simpler and clearer.
Class template deduction makes me drool a bit:
http://en.cppreference.com/w/cpp/language/class_template_deduction
Yet, I won't miss it nowhere nearly as badly as I miss C++11 features.
As I've been saying, IMO it's reasonable compiler availability
in distros that should matter. GCC 7, which will be the first
release to fully support C++17 (or at least close enough) is not
even released yet.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-13 12:12 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 16:46 [PATCH 0/3] More cleanup elimination / gdb::unique_ptr Pedro Alves
2016-10-10 16:46 ` [PATCH 3/3] 'struct parse_expression *' -> gdb::unique_ptr<expression> Pedro Alves
2016-10-10 16:46 ` [PATCH 1/3] Introduce gdb::unique_ptr Pedro Alves
2016-10-10 17:49 ` Simon Marchi
2016-10-10 18:03 ` Pedro Alves
2016-10-11 6:48 ` Metzger, Markus T
2016-10-11 10:23 ` Pedro Alves
2016-10-11 10:53 ` Andreas Schwab
2016-10-11 11:17 ` Metzger, Markus T
2016-10-11 11:43 ` Pedro Alves
2016-10-11 13:58 ` Yao Qi
2016-10-11 14:05 ` Trevor Saunders
2016-10-11 12:16 ` Joel Brobecker
2016-10-11 13:46 ` Pedro Alves
2016-10-11 14:47 ` Joel Brobecker
2016-10-11 15:17 ` Eli Zaretskii
2016-10-11 16:24 ` Pedro Alves
2016-10-11 16:58 ` Eli Zaretskii
2016-10-11 17:41 ` Pedro Alves
2016-10-11 18:37 ` Eli Zaretskii
2016-10-11 19:19 ` Pedro Alves
2016-10-11 20:47 ` Eli Zaretskii
2016-10-11 21:32 ` Pedro Alves
2016-10-12 6:34 ` Eli Zaretskii
2016-10-12 8:11 ` Metzger, Markus T
2016-10-12 9:31 ` Eli Zaretskii
2016-10-12 10:12 ` Pedro Alves
2016-10-12 11:05 ` Eli Zaretskii
2016-10-12 11:25 ` Pedro Alves
2016-10-12 11:45 ` Eli Zaretskii
2016-10-13 12:12 ` Pedro Alves [this message]
2016-10-12 10:28 ` Pedro Alves
2016-10-12 11:07 ` Eli Zaretskii
2016-10-12 11:19 ` Pedro Alves
2016-10-12 11:41 ` Eli Zaretskii
2016-10-12 11:55 ` Pedro Alves
2016-10-13 0:38 ` [PATCH] Enable C++11 starting with gcc 4.8 (was: Re: [PATCH 1/3] Introduce gdb::unique_ptr) Pedro Alves
2016-10-13 0:45 ` [PATCH 1/2] gdb: Import AX_CXX_COMPILE_STDCXX from the GNU Autoconf Archive Pedro Alves
2016-10-13 0:45 ` [PATCH 2/2] gdb: Enable C++11 if available Pedro Alves
2016-10-12 9:37 ` [PATCH 1/3] Introduce gdb::unique_ptr Pedro Alves
2016-10-12 10:51 ` Eli Zaretskii
2016-10-12 11:15 ` Pedro Alves
2016-10-12 11:40 ` Eli Zaretskii
2016-10-12 11:45 ` Jan Kratochvil
2016-10-12 11:56 ` Luis Machado
2016-10-12 12:03 ` Eli Zaretskii
2016-10-13 9:07 ` Jan Kratochvil
2016-10-13 10:07 ` Eli Zaretskii
2016-10-13 10:27 ` Pedro Alves
2016-10-13 13:22 ` Eli Zaretskii
2016-10-13 13:36 ` Pedro Alves
2016-10-13 13:59 ` Eli Zaretskii
2016-10-13 14:04 ` Pedro Alves
2016-10-13 15:06 ` Joel Brobecker
2016-10-13 10:46 ` Jan Kratochvil
2016-10-13 11:15 ` Pedro Alves
2016-10-13 13:28 ` Eli Zaretskii
2016-10-13 13:42 ` Pedro Alves
2016-10-13 14:07 ` Eli Zaretskii
2016-10-11 19:23 ` Simon Marchi
2016-10-11 20:54 ` Eli Zaretskii
2016-10-11 21:28 ` Simon Marchi
2016-10-12 6:23 ` Eli Zaretskii
2016-10-11 21:16 ` Jan Kratochvil
2016-10-11 17:15 ` Luis Machado
2016-10-11 18:21 ` Pedro Alves
2016-10-10 16:58 ` [PATCH 0/3] More cleanup elimination / gdb::unique_ptr Pedro Alves
2016-10-16 7:05 ` Tom Tromey
2016-10-17 13:57 ` Pedro Alves
2016-10-17 14:07 ` Tom Tromey
2016-10-17 14:59 ` Pedro Alves
2016-10-20 13:46 ` 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=32e74745-a5d6-e6b9-b699-d303580f2c92@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=markus.t.metzger@intel.com \
--cc=simon.marchi@ericsson.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