--- Comment #16 from jwakely dot gcc at gmail dot com 2010-01-21 19:00
---
Shouldn't it get the same error as for this case?
template
T foo() { return T(); }
int main()
{
&foo;
}
That example can be made valid like so:
int (*pf)() = &foo;
Which demo
--- Comment #3 from jwakely dot gcc at gmail dot com 2010-01-06 10:42
---
The linker error alone doesn't make the root cause obvious, but it's a fairly
well known and well documented problem:
http://www.parashift.com/c++-faq-lite/strange-inheritance.html#faq-23.10
--- Comment #5 from jwakely dot gcc at gmail dot com 2009-07-24 10:29
---
(In reply to comment #4)
> I think this is invalid because K is used in a non-deduced context
Which is the same problem as with the original testcase - this is not a bug in
gcc.
According to 14.5.
--- Comment #4 from jwakely dot gcc at gmail dot com 2009-07-24 10:12
---
(In reply to comment #3)
> Simple case :
>
>
> template struct A {};
> template struct B { struct Inner {}; };
>
> template
> struct A::Inner> {};
>
>
> 4.1.2/VS2005 com
--- Comment #6 from jwakely dot gcc at gmail dot com 2009-06-23 18:32
---
This seems to be fixed in all open branches (4.3+)
--
jwakely dot gcc at gmail dot com changed:
What|Removed |Added
--
jwakely dot gcc at gmail dot com changed:
What|Removed |Added
CC||jwakely dot gcc at gmail dot
--- Comment #4 from jwakely dot gcc at gmail dot com 2009-06-22 14:49
---
bug 14410 and also bug 5583 :)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14990
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
--
To
--- Comment #2 from jwakely dot gcc at gmail dot com 2009-06-22 14:38
---
See http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#103
"For associative containers where the value type is the same as the key type,
both iterator and const_iterator are constant iterators.
8 matches
Mail list logo
