From: Mike Stump <mikestump@comcast.net>
To: James Youngman <jay@gnu.org>
Cc: gcc-patches@gcc.gnu.org, "Antonio Diaz Diaz" <antonio@gnu.org>,
"Bruno Haible" <bruno@clisp.org>,
"Niels Möller" <nisse@lysator.liu.se>,
tom@tromey.com, "Pedro Alves" <palves@redhat.com>
Subject: Re: CFV: "C++ programming in GNU" interest group (possibly including coding standard development)
Date: Thu, 30 May 2019 19:13:00 -0000 [thread overview]
Message-ID: <BC04C5D4-2EFE-4877-853A-D0882C133FDB@comcast.net> (raw)
In-Reply-To: <CAGwX764gSdmmT4E5W0MuwywZcPHpO=RZX1en4DQ7x=B8DBUSGg@mail.gmail.com>
On May 30, 2019, at 10:55 AM, James Youngman <jay@gnu.org> wrote:
> I'm looking into creating a C++ coding standard for GNU programs.
So, parts of how we do C++ isn't really relevant to a larger community. We at times cater to a C legacy and in a pure C++ project, there may be no need to do this.
ChangeLogs are debatable, and a project might want to option out of them. We've talk about this from time to time, but haven't decided to do that.
We sometimes talk about significantly older language standards. I'd like to think most project would update which language standard they use just a wee bit faster than we do.
But, all in all, sounds like a reasonable thing to do. One skilled it the art of C++ and coding standards should be able to tease out the things that makes less sense I'd like to think.
next prev parent reply other threads:[~2019-05-30 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGwX766NLE9L36Zno-r3VHOpxxnVfk37nswN4Be-MpW=YGrpug@mail.gmail.com>
[not found] ` <CAGwX765iLF713niK+Lo7s=Fg6EjfWZZE2fdznpOzv-SwOiZcpA@mail.gmail.com>
[not found] ` <CAGwX766v9S+OSdhJDEjU2EhYEDb_2GLeOpuYGn4-wOOVPHFi4Q@mail.gmail.com>
2019-05-30 18:11 ` Fwd: " James Youngman
2019-05-30 19:13 ` Mike Stump [this message]
2019-05-31 1:27 ` Joseph Myers
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=BC04C5D4-2EFE-4877-853A-D0882C133FDB@comcast.net \
--to=mikestump@comcast.net \
--cc=antonio@gnu.org \
--cc=bruno@clisp.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jay@gnu.org \
--cc=nisse@lysator.liu.se \
--cc=palves@redhat.com \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).