[C++-sig] can these exports be avoided
Hans Meine
meine at informatik.uni-hamburg.de
Mon Nov 10 10:28:48 CET 2008
On Monday 10 November 2008 08:56:14 Gennadiy Rozental wrote:
> It can be resolved with additional export for class Derived:
>
> bp::class_<Derived,bp::bases<Base>,noncopyable>( "Derived", bp::no_init );
>
> In which case above print statement starts to show mymodule.Derived.
AFAICS that's the proper solution.
> But I
> would really prefer to avoid these exports for derived classes. After all
> RTTI information should shoe Boost.Python whole hierarchy, isn't it?
I don't know much about RTTI, but it was my impression that boost::python has
no (portable) way of automatically deriving inheritance trees.
You might want to try py++ if you don't want to write the export code
yourself.
HTH,
Hans
More information about the Cplusplus-sig
mailing list