What you describe sounds like GCC is getting confused. It may have run
into wrong code, but the error message may be caused by a wrong
interpretation of what you wanted to do.
The fact that things work if you reduce the number of arguments, and the
fact that you had to increase BOOST_PYTHON_MAX_ARITY suggests that
perhaps some of the code inside boost.python does not support the arity
of your call (and isn't configurable via BOOST_PYTHON_MAX_ARITY, so the
compiler couldn't find a matching function for your call. Then, instead
of telling you that it couldn't find a match, it thought you may have
missed qualification (etc.).
However, to substantiate this speculation, I'd need to see the code at
the call site. But the source is so noisy due to all the macros that
it's impossible to see. Could you send a preprocessed source of the
relevant bits ?
Thanks,
Stefan
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig
