> for example I noticed that in this release you make use of "boost::python::pure_virtual" which is
> correct but causes me lots of headaches :) , here is a short explanation of the problem:
> ""boost::python::pure_virtual" is a custom "visitor" that adds a default implementation
> (function "pure_virtual_called") which raises an exception.

I noticed that boost::python::pure_virtual is only used for pure virtual public methods and not for
pure virtual protected methods, is this intentional? I think that boost::python::pure_virtual
should be used in pure virtual protected methods too.

Screensaver e Sfondi: personalizza il tuo PC con Messenger!