[Pyrex] cdef public class bug/problems

[Simon Burton]

On Tue, 22 Nov 2005 11:42:39 +1300
Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:

> > Also, I just don't see how this mechanism can work. It looks totally broken.
> 
> Using .pxi files for cross-pyx extension type access
> is really an obsolete mechanism (superseded by cimport)
> so it's quite possible that it no longer works correctly.

OK, well get rid of it.

> 
> > Don't we need to append the FooObj to the declaration in foo.pxi ?
> > And shouldn't it all be inside a ' cdef extern from "foo.h" ' ?
> 
> As far as I remember, the idea was that Pyrex generates
> C declarations for the type and object structs independently
> for each .pyx which includes the .pxi. Since they're all
> generated from the same Pyrex definition, they should all
> agree with each other.
> 

Don't we need the extern from "foo.h" so that the final .c file #include's this file.

I'm having a look at cimport now. At first glance it didn't seem to be what I
wanted: i have lots of extension classes distributed across extension
modules with a hierarchical interdependancy.

Simon.

-- 
Simon Burton, B.Sc.
Licensed PO Box 8066
ANU Canberra 2601
Australia
Ph. 61 02 6249 6940
http://arrowtheory.com