Hi Alan, Am Montag, 9. Mai 2005 08:07 schrieb Alan Gauld: > The only advice I'd offer is to stick to a C interface rather > than C++ and provide the OO wrapper at the Python layer.
But thats another layer. A c-interface, swig, and python-abstraction. As
Python function calls are rather slow and I want to make full usage of this
measurement device this may be slow. And there's more code to maintain.
> C is
> much easier to use than C++ and simpler to intregrate with
> Python - which is itself written in C.
I have found several examples for this chip and win32 (but with other
firmware) in c and c++. I will evaluate both, I think. What kind of
problems is to be expected when integrating c++ with python (vs. c with
python)?
> Also a C library is
> more open in that it can be used by other projects who may
> not have an OO language to map to C++.
Ah yes, allways make your code reuseable for others. Another point for c.
Thanks for your advices!
Dave
pgpD30Qp6qG3F.pgp
Description: PGP signature
_______________________________________________ Tutor maillist - [email protected] http://mail.python.org/mailman/listinfo/tutor
