From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
Subject: Re: Go C++ only
Date: Thu, 01 Sep 2016 18:22:00 -0000 [thread overview]
Message-ID: <5479c5a0-a346-1718-5573-eeb4b19bc9db@redhat.com> (raw)
In-Reply-To: <410fa84696e520ca3845c841fc7391b8@simark.ca>
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.
> I suppose we'll end up copying
> what GCC does for the most part, but it should be clear.
Right, the proposal is to follow GCC's conventions:
https://sourceware.org/gdb/wiki/cxx-conversion#Coding_conventions
Naturally we'll need to update the coding standards
pages to mention C++ and point at that:
https://sourceware.org/gdb/wiki/Internals%20Coding-Standards
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-09-01 18:22 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 [this message]
2016-09-01 18:33 ` Simon Marchi
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=5479c5a0-a346-1718-5573-eeb4b19bc9db@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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