From: Josh C. <jc...@nc...> - 2009-09-10 14:02:05
|
On Thu, 10 Sep 2009, Ted Ross wrote: > Thanks for the quick responses. I was confused by the fact that swig > generates Python code as well as the C++ code. The generated Python proxy > class is only needed in the "Python-owned" case. The "C++-owned" case is > covered by not using the proxy class but using the pointer (actually a > PyObject) directly. You should get back a proxy class instance when a function returns a pointer to a C++ class instance (or a reference, or an instance). It's not a question of necessity but of desirability. You shouldn't see a "raw" pointer (a PySwigObject) unless the class is not properly wrapped, in which case the proxy class will not exist. Josh |