[PyKDE] Heirarchy of header files !!

[Jonathan Gardner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 14 August 2003 18:27, Paul F. Kunz wrote:
> >>>>> On Thu, 14 Aug 2003 21:10:51 -0400, "satish k.chimakurthi"
> >>>>> <skchim0 at engr.uky.edu> said:
> >
> > Hi Phil, Thanks for your response.
> >
> > I have a huge software library written in C++...I have nearly 50
> > headerfiles in it....I wrote a small code for my application using
> > some classes which are defined in some of the header files
>
>    Unless you need to interface to PyQt, I would recommend that you do
> NOT use SIP.  SIP is completely undocumented and does some pretty
> wierd things.  I'm probably biased just after spending three full days
> trying to get something to work, but I find SIP violates one of C++'s
> strenghts: "If it compiles and links, there's probably not going to be
> any run time errors".  With SIP run time errors can easily happen and
> it reminds me of days I used to program in Fortran.
>

This is due to python, not due to poor implementation of sip.

About it being undocumented -- that is untrue. There are at least two 
documents that I have found that describe how to use sip, enough that I 
could put togethre a sip file for PostgreSQL's C API.

I would give sip a try at least. Most C++ header files need only slight 
modifications to translate to sip.

As far as the hierarchy of header files, you should write sip files only for 
the functions that you want exposed in Python.

- -- 
Jonathan Gardner
jgardner at jonathangardner.net
Live Free, Use Linux!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/PD3DWgwF3QvpWNwRAvaLAKDsxyUBlxQ5cSIFDbHnYyIn1S7ZsQCeKUAl
32X94ewZzyEjYo429MVxZ20=
=IFpX
-----END PGP SIGNATURE-----