https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
Paolo Carlini changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
--- Comment #11 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Wed Sep 9 16:48:13 2015
New Revision: 227593
URL: https://gcc.gnu.org/viewcvs?rev=227593&root=gcc&view=rev
Log:
2015-09-09 Paolo Carlini
PR c++/53184
* do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
Paolo Carlini changed:
What|Removed |Added
CC||blue.dragan+gcc at gmail dot
com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
--- Comment #9 from Paolo Carlini ---
... and of course a clearer wording for the warning itself.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
--- Comment #8 from Paolo Carlini ---
Somebody could suggest an appropriate name for the warning. Then a patchlet
would be easy to do and also easy to approve I think (naming warnings is in
general a sensible idea)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
--- Comment #7 from Jonathan Wakely ---
I've just come across a case where an option to disable that warning would be
handy: We have a foo.cc file defining some classes in an anon namespace. A unit
test does #include "foo.cc" so it can test the im
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
--- Comment #6 from Nathan Ridge ---
(In reply to Jason Merrill from comment #4)
> (In reply to comment #3)
> > Because then the anonymous class has the name "Foo" for linkage purposes,
> > and
> > has external linkage. When Foo referes to the c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
Paolo Carlini changed:
What|Removed |Added
CC||zeratul976 at hotmail dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
--- Comment #4 from Jason Merrill 2012-05-02
17:23:09 UTC ---
(In reply to comment #3)
> Because then the anonymous class has the name "Foo" for linkage purposes, and
> has external linkage. When Foo referes to the const or volatile qualified
>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
Jonathan Wakely changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
--- Comment #2 from Orgad Shaneh 2012-05-02 06:56:28
UTC ---
Anonymous types shouldn't produce any warnings. They are very commonly used in
headers needed for both C and C++ projects. The warning is meant for types
inside anonymous namespaces, wh
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53184
--- Comment #1 from Andrew Pinski 2012-05-02
06:25:50 UTC ---
>foo.cpp:5:16: warning: 'Bar' has a field 'Bar::foo' whose type uses the
anonymous namespace [enabled by default]
The warning just needs to be worded better but otherwise it is correc
13 matches
Mail list logo
