[Pyrex] possible bug with public function declarations

[Greg Ewing]

Robby Dermody wrote:
> 
> I'm thinking there may be a possible bug with public C function
> declarations in Pyrex 0.93.
> 
> The project is set up so that foo.pyx and bar.pyx are linked together,

Linking two Pyrex-generated modules together isn't
really supported, and strange things might happen if
you try it. You might get away with it if one of them
restricts itself to C-only declarations and operations,
but Pythonish things are likely to go haywire.

All the .pxi stuff is pretty much deprecated now. A
better way to make cross-pyx C calls is to make them
C methods of an extension type. (Directly calling
top-level C functions of another module isn't supported
yet, but may be in a future version.)

-- 
Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
greg.ewing at canterbury.ac.nz	   +--------------------------------------+