[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] sipNew vs sipCpp
From:       Phil Thompson <phil () riverbankcomputing ! co ! uk>
Date:       2004-01-28 8:11:35
Message-ID: 200401280811.35356.phil () riverbankcomputing ! co ! uk
[Download RAW message or body]

On Wednesday 28 January 2004 1:46 am, Claus, Richard wrote:
> Hi,
>
>   I'm upgrading from sip 3.8 to sip 3.10 and noticed that my application
> now fails to compile because the variable sipNew has undergone a name
> change to sipCpp.  Since I didn't find any notes with the package or
> comments on the PyKDE list about this, I'm wondering whether I'm using
> "privileged" information.  Should I be constructing my objects in some
> other way in the %MemberCode block?  At the time that this package was
> coming together (sip 3.3 days) it appeared necessary to do this in order to
> handle various constructor arguments.

You should migrate your %MemberCode to %MethodCode as the former is now 
deprecated and unsupported in SIP 4.x. The latter is much easier to use and 
requires much less handwritten code.

Running SIP with the -w flag will tell you (hopefully) all the things you need 
to change.

Phil

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]