public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Diego Novillo <dnovillo@google.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
	gcc@gcc.gnu.org, 	Basile Starynkevitch <basile@starynkevitch.net>
Subject: Re: status of GCC & C++
Date: Sun, 25 Mar 2012 22:01:00 -0000	[thread overview]
Message-ID: <CAAiZkiAD4bJEFu9uhyDyYzchwCGG5nbUe0pY025_Bampw9Xz0w@mail.gmail.com> (raw)
In-Reply-To: <CAD_=9DRyL8ABYhJAjWdr-=e65A-Xi7tN3sMwFTZFvkmgckLtGg@mail.gmail.com>

On Sun, Mar 25, 2012 at 4:45 PM, Diego Novillo <dnovillo@google.com> wrote:

> 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.

I agree with Diego that to start building only with a C++ compiler, we
do not need
to have approved a C++ coding convention.

I also think that the current wiki page is still at brainstorming
phase than a sufficiently
complete and coherent set.  It needs further flushing.  For example, I do not
believe it makes sense to ban both simple templates (for writing containers)
and virtual functions (or to that matter multiple inheritance).  There
are forms of those
features that need to be properly restricted (e.g. it would a real
mistake to go
banana with the "advanced" template (meta)programming stuff.)
Similarly, some of the
control/flow and path can be significantly reduced (and bugs fixed!)
if simple exception
handling is allowed -- think of all those bugs caused by failure to
exit early on
error_mark_node.

-- Gaby

  reply	other threads:[~2012-03-25 22:01 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 [this message]
2012-03-28 19:50           ` Eric Botcazou
     [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=CAAiZkiAD4bJEFu9uhyDyYzchwCGG5nbUe0pY025_Bampw9Xz0w@mail.gmail.com \
    --to=gdr@integrable-solutions.net \
    --cc=basile@starynkevitch.net \
    --cc=dnovillo@google.com \
    --cc=ebotcazou@adacore.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).