On 22-Mar-05, at 12:34 PM, Jim Bublitz wrote:
It appears that when passing Python instances back into C++ you are
creating a second, unrelated smart pointer. Unless KSharedPtr is
maintaining a mapping of C++ pointers, the pointer that gets passed in
is getting an extra reference added to it that w
On Tuesday 22 March 2005 10:04, James Emerton wrote:
> On 22-Mar-05, at 12:23 AM, Jim Bublitz wrote:
>
>
> > It seems to me Python is taking care of all of the ref counting in
> > this case -
> > there might be pathological cases where either the C++ instance of the
> > template type or the Python
> It would be really nice if Phil would add some form of smart pointer
> support to SIP. *hint hint* =) I may write something myself
> eventually, if I can figure out what it should look like.
What it should look like is what I've stumbled over before.
Phil
__
On 22-Mar-05, at 12:23 AM, Jim Bublitz wrote:
It seems to me Python is taking care of all of the ref counting in
this case -
there might be pathological cases where either the C++ instance of the
template type or the Python instance get orphaned (no corresponding
object on
"the other side"). Mos
On Monday 21 March 2005 09:29, James Emerton wrote:
> I am rather new to PyQt/SIP and looking for a hint or two.
> The application in which I am embedding Python has a fairly extensive
> (non-Qt) API, with a Qt UI sitting on top. The API makes extensive use
> of refcounted smart pointers (boost::
I am rather new to PyQt/SIP and looking for a hint or two.
The application in which I am embedding Python has a fairly extensive
(non-Qt) API, with a Qt UI sitting on top. The API makes extensive use
of refcounted smart pointers (boost::shared_ptr) to abstract interface
classes.
So far, I beli
