From: Nick Clifton <nickc@redhat.com>
To: Christian Biesinger <cbiesinger@google.com>, binutils@sourceware.org
Cc: gdb@sourceware.org
Subject: Re: Allow C99/C11 in bfd?
Date: Fri, 24 Jan 2020 11:50:00 -0000 [thread overview]
Message-ID: <f9e166e2-a473-a521-d091-595d22b694da@redhat.com> (raw)
In-Reply-To: <CAPTJ0XGOYJf9Q_bdgHcLe9+PUp910NxXQsswfVht-=dBRbdDWA@mail.gmail.com>
Hi Christian,
> I noticed that bfd is currently using C89. I was wondering if there
> are any thoughts on allowing C99/C11 in there? It would be nice to be
> able to declare variables at the time of first use, among other useful
> features.
I would be willing to consider such a change, provided that there are
no strenuous objections...
> (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.
Cheers
Nick
next prev parent reply other threads:[~2020-01-24 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 10:38 Christian Biesinger via binutils
2020-01-24 11:50 ` Nick Clifton [this message]
2020-01-24 13:20 ` Joel Brobecker
2020-01-24 16:34 ` Christian Biesinger via binutils
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=f9e166e2-a473-a521-d091-595d22b694da@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=cbiesinger@google.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).