From: Jason Merrill <jason@redhat.com>
To: Mike Stump <mikestump@comcast.net>
Cc: Volker Reichelt <v.reichelt@netcologne.de>,
David Malcolm <dmalcolm@redhat.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ PATCH] New warning for extra semicolons after in-class function definitions
Date: Mon, 10 Apr 2017 16:54:00 -0000 [thread overview]
Message-ID: <CADzB+2msE9PCdkooJuc+sw9ZY2Mh65xHMBYwvhjwj5frnFyCkQ@mail.gmail.com> (raw)
In-Reply-To: <D1DF55FC-3440-429F-9E52-DA900A56E554@comcast.net>
On Mon, Apr 10, 2017 at 12:32 PM, Mike Stump <mikestump@comcast.net> wrote:
> On Apr 9, 2017, at 1:53 PM, Volker Reichelt <v.reichelt@netcologne.de> wrote:
>>>> +Wextra-semi
>>>> +C++ Var(warn_extra_semi) Warning
>>>> +Warn about semicolon after in-class function definition.
>>>> +
>
>> Right now, the patch enables the warning only for C++.
>> Would it make sense to enable it also for ObjC++?
>
> This is reversed. Always do the exact same thing for Objective-C++ as for C++ (unless there is a compelling reason why not). I don't see any reason why we should avoid Objective-C++ in this case.
Agreed. OK with that change.
Jason
next prev parent reply other threads:[~2017-04-10 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 19:55 Volker Reichelt
2017-04-07 21:22 ` David Malcolm
2017-04-09 20:53 ` Volker Reichelt
2017-04-10 16:32 ` Mike Stump
2017-04-10 16:54 ` Jason Merrill [this message]
2017-04-07 19:58 Volker Reichelt
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=CADzB+2msE9PCdkooJuc+sw9ZY2Mh65xHMBYwvhjwj5frnFyCkQ@mail.gmail.com \
--to=jason@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=v.reichelt@netcologne.de \
/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).