https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85128
--- Comment #12 from Steffen Nurpmeso ---
Or you could compile with -std=c++98
Yes, thanks for the opportunity. I would rather not, the fix was simple and
only affected this class and its specializations (of 383, 315 public
interface).
> (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85128
--- Comment #10 from Steffen Nurpmeso ---
Hello Andrew Pinski!
Ok i have to apologize for not searching in Bugzilla very carefully it seems.
I see now, indeed i was -- even if that sounds inconceivable -- under the
impression that the error mess
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34531
--- Comment #7 from Steffen Nurpmeso ---
Hello Andrew Pinski!
Ok i have to apologize for not searching in Bugzilla very carefully it seems.
I see now, indeed i was -- even if that sounds inconceivable -- under the
impression that the error messa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85128
--- Comment #5 from Steffen Nurpmeso ---
Sorry for not providing a test case.
The C++ standard is clear here about this case too.
I have a PDF version of a 2014 draft, and i would not see that in case your
words are implying that gcc is righ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85128
--- Comment #3 from Steffen Nurpmeso ---
One more, and just to point that out. This code will in a not too distant
future see its 20th birthday (though not updated for long). It has been
developed on Linux and FreeBSD with the wonderful (me thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85128
--- Comment #2 from Steffen Nurpmeso ---
Excuse me please, but in how far is
namespace X{
class A;
class B;
}
class X::A{..};
class X::B { typedef X::A A; }
invalid C++? Which standard added that??
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: steffen at sdaoden dot eu
Target Milestone: ---
Hi, my first post here.
So i have no idea, all i can say is what the subject says, that clang gets it
right, and here is
