Hi all,
Is it my imagination, or is there no implementation of sipSetBool
is Sip 4.4 or sip-snapshot-20060325?
Is this Sip's way of punishing us for statically linking our
sip-generated bindings into the program? :-)
Nigel
-----------------
There are no unresolved sip symbols for sip 4.3.2:
[EMAIL PROTECTED] ~/Wares/libs/sip-4.3.2/siplib $ ldd -r sip.so
linux-gate.so.1 => (0xffffe000)
...
For 4.4 sipSetBool is unresolved:
[EMAIL PROTECTED] ~/Wares/libs/sip-4.4/siplib $ ldd -r sip.so
linux-gate.so.1 => (0xffffe000)
...
undefined symbol: sipSetBool (./sip.so)
-----------------
[EMAIL PROTECTED] ~/Wares/libs/sip-4.3.2/siplib $ grep sipSetBool *.h *.c
sipint.h:void sipSetBool(void *ptr,int val);
siplib.c:
sipSetBool(va_arg(va,void *),(int)v);
siplib.c: sipSetBool(va_arg(va,void
*),(int)v);
[EMAIL PROTECTED] ~/Wares/libs/sip-snapshot-20060325/siplib $ grep sipSetBool
*.h *.c
sipint.h:void sipSetBool(void *ptr,int val);
siplib.c:
sipSetBool(va_arg(va,void *),v);
siplib.c: sipSetBool(va_arg(va,void *),v);
siplib.c:
sipSetBool(va_arg(va,void *),(arg == Py_True));
_______________________________________________
PyKDE mailing list [email protected]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
