Re: [Pyobjc-dev] Passing objects between PyObjc and SWIG
Brought to you by:
ronaldoussoren
|
From: Ronald O. <ron...@ma...> - 2008-03-20 14:14:18
|
On 20 Mar, 2008, at 11:27, Kyle Johnson wrote:
>
>
> A semi-related question: if I'm getting objects of type PyObjCPointer
> when I do not import the PyObjc Quartz lib, but then I get objects of
> "actual" types ("core-foundation class CGContextRef" in this case)
> when I include the PyObjc Quartz lib, is that an indication that I
> _must_ include the Quartz lib?
Yes. Which methods return a PyObjCPointer when you don't import Quartz?
>
>> From my digging so far, I think that just dealing with PyObjCPointers
> and SWIG would be relatively simple; I just have that nagging idea
> that PyObjCPointers are results of errors though. :)
PyObjCPointers are definitely something you don't want to use. They
are the last resort for wrapping an arbitrary C pointer and should
never occur when a library is properly wrapped.
Ronald
|