Michael Abshoff wrote: > Jason Evans wrote: >> I don't understand what portability problem you're referring to. >> Assuming that size_t was defined to be unsigned long or unsigned long >> long (depending on the platform), why would there be a problem? > > Code created by Cython on one platform ought to work on another > platform. And since Python.h provides that info about the size of size_t > for you why bother to implement that independently?
Ah, okay. I had to give up on the portability of Cython-generated code in order to add the ability to conditionally support mpi4py, so I haven't really been thinking in terms of portable Cython output lately. Thanks for the explanation. Jason _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
