[C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject (original) (raw)
Roman Yakovenko roman.yakovenko at gmail.com
Sun Dec 18 11:47:16 CET 2005
- Previous message: [C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject
- Next message: [C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/15/05, Shin-ichi MORITA <shin1_morita at yahoo.co.jp> wrote:
Hi David and Roman,
I'm confused! You say "If you override init(), you must call module1.Derived.init()", don't you? But I do NOT override init() here. Again... everything is ok except for module1. Please check out "testowner.tar.bz2" which I sent before.
I checked your test case on windows (vc 7.1) and it works as expected. It seems, that I can not help you.
Sorry.
Anyway, my concern is "boost::python::detail::wrapperbase should be polymorphic? (or should have virtual destructor?)".
Thanks. David Abrahams <dave at boost-consulting.com> wrote: > > I think that init() is implicitly called > because > > init() is not overriden. > > It is not. Listen to Roman.
-------------------------------------- STOP HIV/AIDS. Yahoo! JAPAN Redribbon Campaign 2005 http://pr.mail.yahoo.co.jp/redribbon/
C++-sig mailing list C++-sig at python.org http://mail.python.org/mailman/listinfo/c++-sig
- Previous message: [C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject
- Next message: [C++-sig] returning a wrapper instance exposed in the other module is not converted to its owner PyObject
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]