Re: [PyQt] References returned from C++

2008-06-23 Thread Arve Knudsen
On 6/22/08, Phil Thompson <[EMAIL PROTECTED]> wrote: > On Sun, 22 Jun 2008 12:53:41 +0200, "Arve Knudsen" <[EMAIL PROTECTED]> > wrote: > > > How does one normally treat references returned by SIP-wrapped C++ > > objects? I just determined a segmentation fault in my program resulted > > from an o

Re: [PyQt] References returned from C++

2008-06-22 Thread Phil Thompson
On Sun, 22 Jun 2008 14:26:20 +0200, Detlev Offenbach <[EMAIL PROTECTED]> wrote: > On Sonntag, 22. Juni 2008, Phil Thompson wrote: >> On Sun, 22 Jun 2008 12:53:41 +0200, "Arve Knudsen" > <[EMAIL PROTECTED]> >> >> wrote: >> > How does one normally treat references returned by SIP-wrapped C++ >> > obj

Re: [PyQt] References returned from C++

2008-06-22 Thread Phil Thompson
On Sun, 22 Jun 2008 14:12:45 +0200, Giovanni Bajo <[EMAIL PROTECTED]> wrote: > On Sun, 2008-06-22 at 12:41 +0100, Phil Thompson wrote: >> On Sun, 22 Jun 2008 12:53:41 +0200, "Arve Knudsen" > <[EMAIL PROTECTED]> >> wrote: >> > How does one normally treat references returned by SIP-wrapped C++ >> > o

Re: [PyQt] References returned from C++

2008-06-22 Thread Detlev Offenbach
On Sonntag, 22. Juni 2008, Phil Thompson wrote: > On Sun, 22 Jun 2008 12:53:41 +0200, "Arve Knudsen" <[EMAIL PROTECTED]> > > wrote: > > How does one normally treat references returned by SIP-wrapped C++ > > objects? I just determined a segmentation fault in my program resulted > > from an object fi

Re: [PyQt] References returned from C++

2008-06-22 Thread Giovanni Bajo
On Sun, 2008-06-22 at 12:41 +0100, Phil Thompson wrote: > On Sun, 22 Jun 2008 12:53:41 +0200, "Arve Knudsen" <[EMAIL PROTECTED]> > wrote: > > How does one normally treat references returned by SIP-wrapped C++ > > objects? I just determined a segmentation fault in my program resulted > > from an obj

Re: [PyQt] References returned from C++

2008-06-22 Thread Phil Thompson
On Sun, 22 Jun 2008 12:53:41 +0200, "Arve Knudsen" <[EMAIL PROTECTED]> wrote: > How does one normally treat references returned by SIP-wrapped C++ > objects? I just determined a segmentation fault in my program resulted > from an object first being obtained as a reference (in the C++ sense) > from

[PyQt] References returned from C++

2008-06-22 Thread Arve Knudsen
How does one normally treat references returned by SIP-wrapped C++ objects? I just determined a segmentation fault in my program resulted from an object first being obtained as a reference (in the C++ sense) from a C++ method, and then destroyed with the parent object. Does one normally keep in min