From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, markus.t.metzger@intel.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Introduce gdb::unique_ptr
Date: Wed, 12 Oct 2016 09:37:00 -0000 [thread overview]
Message-ID: <a60ed649-b5cf-e9ed-9bcd-b9ab172f8e75@redhat.com> (raw)
In-Reply-To: <83oa2qaxe7.fsf@gnu.org>
On 10/12/2016 07:34 AM, Eli Zaretskii wrote:
>>> I'm still arguing because you all but decided to declare that to enjoy
>>> GDB to its fullest one has from now on to have GCC 6.x. GCC 6.1 was
>>> released just this April, so it sounds too drastic to require it only
>>> a few months later.
>>
>> Eli, I've repeatedly told you that that's completely false. No one
>> is suggesting that.
>
> Jan just did.
No he didn't. That's another straw man argument.
Jan said, in full:
> The discussion is about C++11. LLVM+LLDB have switched to C++11 in 2014 and
> they haven't looked back.
>
> I see the C++11 discussion pointless, where is the system which really needs
> GDB and which still cannot compile C++11? Why to waste manyears on bugs which
> can no longer exist with C++11?
>
> The discussion should be when to switch to C++17 as that removes another tons
> of crap like gnulib.
He's saying that we should just require C++11 and be done with it.
And then he concluded with a (hopefully tongue-in-cheek) remark about
C++17, which (hopefully) is obvious we're not going to be requiring
that anytime soon...
Fact: Nowhere did he say that we will now require GCC 6.1.
Requiring C++11 would mean requiring GCC around 4.8, NOT GCC 6.1.
> So "completely false" is completely false.
You're repeated claims that people are suggesting to require
GCC 6.1 are provably false.
In any case, Jan's reply came after all our discussions, and I'm
not Jan. If someone comes in and suggests to actually require GCC 6.1,
then I'll stop saying that nobody is suggesting that, and instead say
that I'd strongly object it.
> And what
> you are suggesting, while not as radical as what Jan says, will still
> get us there soon enough.
There's no Trojan here. If you don't trust me, then I don't know
what else I can do...
>> At this point I have to wonder whether you're not listening on
>> purpose.
>
> This goes both ways, you know. And I hope you understand how it could
> be an insult when actually written in a discussion.
I did not mean it as an insult. I apologize if it sounded that way.
And conversely, I hope you understand how repeated straw man
arguments even after they're categorically dismissed could be
taken as an insult.
> Why do we need to get to this level each time I happen to disagree with something here?
> It's the reason why I speak so little here about my opinions on the
> various matters.
I don't know. IMO, it would have helped a lot if the discussion
would have not had so many straw man arguments thrown my way.
Can we please redirect all this energy to actual technical
discussions, please? Does anyone want to comment on the
the patch itself and on the smart pointer design?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-12 9:37 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
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 ` Pedro Alves [this message]
2016-10-12 10:51 ` [PATCH 1/3] Introduce gdb::unique_ptr 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=a60ed649-b5cf-e9ed-9bcd-b9ab172f8e75@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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