From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Go C++ only
Date: Thu, 01 Sep 2016 18:33:00 -0000 [thread overview]
Message-ID: <72276a8218ef0e667097dc3fb152c518@simark.ca> (raw)
In-Reply-To: <5479c5a0-a346-1718-5573-eeb4b19bc9db@redhat.com>
On 2016-09-01 14:22, Pedro Alves wrote:
> On 09/01/2016 07:07 PM, Simon Marchi wrote:
>
>> Are there some guidelines about which C++ features we can use or not?
>
> I think the biggest guideline so far is that people still want to build
> gdb on systems with compilers that predate C++11, so we're stuck with
> C++03 for the moment.
>
>> Perhaps some precisions about the coding style, for C++-specific
>> constructs (e.g. initializer lists).
>
> List initialization is C++11, so it's out, at least for now.
Oh, I meant the list of members to initialize in a constructor (the list
after the colon), that's not C++11 I believe. I see it's all discussed
in the gcc coding convention page.
And to complete my answer on the original subject, I think it's fine to
wait until 7.12 is out before checking in anything that is C++-only.
The wait has been long already, a few weeks won't change much :).
next prev parent reply other threads:[~2016-09-01 18:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 17:32 Pedro Alves
2016-09-01 17:48 ` Dmitry Samersoff
2016-09-01 18:07 ` Simon Marchi
2016-09-01 18:22 ` Pedro Alves
2016-09-01 18:33 ` Simon Marchi [this message]
2016-09-01 18:48 ` Pedro Alves
2016-09-01 18:56 ` Pedro Alves
2016-09-01 18:36 ` Andrew Pinski
2016-09-01 19:01 ` Eli Zaretskii
2016-09-01 19:07 ` Pedro Alves
2016-09-01 18:17 ` Joel Brobecker
2016-09-02 10:01 ` Yao Qi
2016-09-02 10:15 ` Pedro Alves
2016-09-02 15:34 ` Sergio Durigan Junior
2016-09-02 20:10 ` Sergio Durigan Junior
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=72276a8218ef0e667097dc3fb152c518@simark.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@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