I've been bitten by this one as well. I _think_ gcc is wrong here, the
same error is raised when taking the address of a member fn in another
(of the same class).
The compiler should be able to determine the correct scope in both these
cases.
The only workaround is to used the verbose form that keeps gcc happy.
Ian
--
Ian Collins
Masuma Ltd,
Christchurch
New Zealand.