Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eldlistmailingz at tropicsoft dot com
Target Milestone: ---
The code, as test_predicate.cpp:
template < typename T, T *d > class atmp { atmp() {} };
template < typename T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92319
Edward Diener changed:
What|Removed |Added
CC||eldlistmailingz@tropicsoft.
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eldlistmailingz at tropicsoft dot com
Target Milestone: ---
When the variadic arguments of a macro whose replacement lists
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65547
--- Comment #7 from Edward Diener ---
(In reply to Jonathan Wakely from comment #5)
> And as has been documented forever, the way to get diagnostics for GNU
> extensions that contradict the ISO standard is the -pedantic switch:
>
> https://gcc.g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65547
--- Comment #6 from Edward Diener ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Edward Diener from comment #3)
> > Where do you get the idea that the standard doesn't require an error, it
> > requires a diagnostic message ?
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65547
--- Comment #3 from Edward Diener ---
Where do you get the idea that the standard doesn't require an error, it
requires a diagnostic message ?
It clearly is a violation of the C++11 standard according to the section and
paragraph I cited in my b
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eldlistmailingz at tropicsoft dot com
Given the variadic macro:
#define VMACRO(x,...) x __VA_ARGS__
if it is invoked with
VMACRO(1)
a compiler error should occur
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48157
Summary: Unable to match function call to member function
template
Product: gcc
Version: 4.5.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
