From: Joel Brobecker <brobecker@adacore.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Christian Biesinger <cbiesinger@google.com>,
binutils@sourceware.org, gdb@sourceware.org
Subject: Re: Allow C99/C11 in bfd?
Date: Fri, 24 Jan 2020 13:20:00 -0000 [thread overview]
Message-ID: <20200124132004.GA7409@adacore.com> (raw)
In-Reply-To: <f9e166e2-a473-a521-d091-595d22b694da@redhat.com>
> > (I'm not even going to ask about C++, although I think that would be nice)
>
> Bah! Real programmers don't use C++! Just joking of course,
> but I seriously doubt that we will want to change the code base
> now. Speaking personally I am much more comfortable with C
> than with C++, but that is probably just me.
The way the Pro C++ members of the GDB community approached the
suggestion was by building a case of what C++ would bring,
concretely, in terms of improvement. They also had a transition
plan. As someone who was _not_ in favor of the switch to C++, I had
to admit that the C++ proponents had some solid points and that
those against did not have a solid counter-argument. It took
a while, as a decision of this magnitude always takes, but
it helped us keep the discussions focused on factual technical
arguments. I thought that worked really way for the GDB group.
Assuming the community is not refusing to even hear about the idea,
how things happened in GDB could be inspiration for how to at least
debate the merits of the change.
Note that the idea might be dead right off the bat if being
usable from C is an objective of the binutils project. For
a relatively low-level library like this one, I wouldn't personally
be surprised.
--
Joel
next prev parent reply other threads:[~2020-01-24 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPTJ0XGOYJf9Q_bdgHcLe9+PUp910NxXQsswfVht-=dBRbdDWA@mail.gmail.com>
2020-01-24 11:50 ` Nick Clifton
2020-01-24 13:20 ` Joel Brobecker [this message]
2020-01-24 16:34 ` Christian Biesinger via gdb
2020-01-28 1:29 ` Alan Modra
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=20200124132004.GA7409@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--cc=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=nickc@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