--- Comment #6 from pcarlini at suse dot de 2006-10-02 20:51 ---
(In reply to comment #5)
> Interesting. The vanilla EDG front end rejects it as expected. I wonder why
> Intel accepts it when neither EDG nor gcc does.
Sorry about the trivial question: Intel in *strict* mode?
--
htt
--- Comment #5 from sebor at roguewave dot com 2006-10-02 19:19 ---
Interesting. The vanilla EDG front end rejects it as expected. I wonder why
Intel
accepts it when neither EDG nor gcc does. Maybe we should open a bug with them
to
find out ;-)
--
http://gcc.gnu.org/bugzilla/show_bu
--- Comment #4 from bkoz at gcc dot gnu dot org 2006-10-02 10:06 ---
s/to/two
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29298
--- Comment #3 from bkoz at gcc dot gnu dot org 2006-10-02 10:05 ---
Thanks Andrew. I agree, this is not permitted by the standard as the enclosing
class is not specialized.
What a bummer. I suppose I can work around this by making a more convoluted
inheritance chain.
This would have
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-09-30 16:00 ---
Dup of PR 16934, PR 15359, PR 8665, and others.
PR 8665 has the best description of why this is not a bug and also has the link
to where in the standard this is invalid so closing as a dup of that bug.
*** This bug
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-09-30 15:56 ---
>From 14.7.2 [temp.expl.spec] paragraph 2:
An explicit specialization shall be declared in the namespace of which the
template is a member,
or, for member templates, in the namespace of which the enclosing clas
