Re: [C++-sig] memory leak with __iadd__

2013-09-26 Thread Neal Becker
Nikolay Mladenov wrote: > On Wed, Sep 25, 2013 at 11:22 AM, Neal Becker wrote: > >> I've been trying to track down a memory leak. When I use the following: >> >> .def ("__iadd__", &hist_t::operator+=, bp::return_self<>()) >> > > but this is no different then any other function def with return

Re: [C++-sig] Boost python simple interfacing

2013-09-26 Thread Kassiopi Kassiopi2
Hi, I apologize for the delayed reply. I was hoping to avoid linking the commandManager into the .so file. I am trying to avoid that because then, I will have to do this for any other module that I create and uses the commandManager. I would prefer to declare it as extern or something similar if

Re: [C++-sig] memory leak with __iadd__

2013-09-26 Thread Nikolay Mladenov
On Wed, Sep 25, 2013 at 11:22 AM, Neal Becker wrote: > I've been trying to track down a memory leak. When I use the following: > > .def ("__iadd__", &hist_t::operator+=, bp::return_self<>()) > but this is no different then any other function def with return_self<> policy (which i do a lot)? wh