--- Comment #6 from manu at gcc dot gnu dot org 2007-01-23 14:13 ---
Could you provide a smaller testcase?
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from igodard at pacbell dot net 2007-01-23 14:54 ---
My goof - sorry to trouble you
--
igodard at pacbell dot net changed:
What|Removed |Added
--- Comment #1 from igodard at pacbell dot net 2007-01-22 20:40 ---
Created an attachment (id=12933)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12933action=view)
compiler output -v
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30548
--- Comment #2 from igodard at pacbell dot net 2007-01-22 20:41 ---
Created an attachment (id=12934)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12934action=view)
source code (compressed)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30548
--- Comment #3 from igodard at pacbell dot net 2007-01-22 20:44 ---
p.s. if the disambiguator template is inserted in front of the call (i.e.
... .template MMIOize ... the the compiler complains that a disambiguating
template keyword can only be used in a template.
--
--- Comment #4 from igodard at pacbell dot net 2007-01-22 21:20 ---
p.p.s. The error depends on the kind of primary in front of the selection and
call. If the primary is a variable then no error, as shown in the previous
line. However, you can also make the error go away by wrapping the
--- Comment #5 from igodard at pacbell dot net 2007-01-22 21:53 ---
OK, found the source of the problem: there's a template function in the base
class and a non-template function of the same name in the derived class, and
the parse is resolving the call to the non-template even though
