pygccxml-development

[pygccxml-development] Memory ownership

[Philip A. <phi...@my...>]

Hello

I'm pretty new to Py++ and Boost::Python.

Consider the following code (taken from the unit tests of my wrapped
library):

        self.logManager.addListener(MockLogListener())

The C++ prototype of the addListener method is:

        void addListener(ILogListener* pListener);


I didn't found a way to specify that the logManager instance is now
responsible of the destruction of the listener object. Several classes
acts this way in my library.

The result is that the logManager now holds an invalid pointer, and will
throw a C++ exception when trying to use it.

Is there any workaround (besides keeping a reference to every object on
the Python-side)?

Re: [pygccxml-development] Memory ownership

[Roman Y. <rom...@gm...>]

On 11/17/06, Philip Abbet <phi...@my...> wrote:
> Hello
>
> I'm pretty new to Py++ and Boost::Python.
>
> Consider the following code (taken from the unit tests of my wrapped
> library):
>
>         self.logManager.addListener(MockLogListener())
>
> The C++ prototype of the addListener method is:
>
>         void addListener(ILogListener* pListener);
>
>
> I didn't found a way to specify that the logManager instance is now
> responsible of the destruction of the listener object. Several classes
> acts this way in my library.

http://boost.org/libs/python/doc/v2/faq.html#ownership

http://language-binding.net/pyplusplus/documentation/inserting_code.html

I hope the links will help you.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/