From: Eric Botcazou <ebotcazou@adacore.com>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org, Basile Starynkevitch <basile@starynkevitch.net>
Subject: Re: status of GCC & C++
Date: Wed, 28 Mar 2012 19:50:00 -0000 [thread overview]
Message-ID: <201203282150.02932.ebotcazou@adacore.com> (raw)
In-Reply-To: <CAD_=9DRyL8ABYhJAjWdr-=e65A-Xi7tN3sMwFTZFvkmgckLtGg@mail.gmail.com>
> Really? To start *writing* in C++, sure we want at least an initial
> version of the coding guidelines. I pointed to those, because they
> look like a reasonable start.
>
> To start *building* in C++, I do not think we need to agree on the
> coding guidelines. We are already doing stages 2 and 3, doing stage 1
> is a straightforward next step.
If we start building in C++, then this would mean that you can start to use
C++ in the code. And we agreed to settle on a set of coding guidelines before
starting to use C++ in the code.
Building stage 1 with a C++ compiler has zero value if you don't use C++ in
the code. It probably even has a negative value, since it gratuitously makes
it harder to build the compiler on exotic platforms.
--
Eric Botcazou
next prev parent reply other threads:[~2012-03-28 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 17:19 Basile Starynkevitch
2012-03-25 17:25 ` Diego Novillo
2012-03-25 17:33 ` Eric Botcazou
2012-03-25 17:44 ` Diego Novillo
2012-03-25 21:37 ` Eric Botcazou
2012-03-25 21:46 ` Diego Novillo
2012-03-25 22:01 ` Gabriel Dos Reis
2012-03-28 19:50 ` Eric Botcazou [this message]
[not found] ` <20120325192843.05bf843acfb715c4bc9cd4aa@starynkevitch.net>
[not found] ` <4F6F5E48.90404@google.com>
2012-03-25 18:31 ` Basile Starynkevitch
2012-03-25 20:11 ` Basile Starynkevitch
2012-03-25 20:21 ` Gabriel Dos Reis
2012-03-25 20:29 ` Marc Glisse
2012-03-26 15:59 ` Configure-time testing for GCC plugins to determine C vs C++? (Was Re: status of GCC & C++) David Malcolm
2012-03-26 17:07 ` Joseph S. Myers
2012-03-26 18:18 ` David Malcolm
2012-03-26 18:33 ` Basile Starynkevitch
2012-03-26 20:34 ` Romain Geissler
2012-03-27 5:53 ` Basile Starynkevitch
2012-03-27 10:23 ` status of GCC & C++ Ludovic Courtès
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=201203282150.02932.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=basile@starynkevitch.net \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.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).