Alexander Schmolck wrote:
> what's the best approach to write C(++)-extension code that has to create a
> python int from a C pointer and vice versa so that it works smoothly on 32 bit
> and 64 platforms (on which sizeof(int) != sizeof(*void)) equally work (under
> unix,mac&windows and with gcc, vc
Alexander Schmolck <[EMAIL PROTECTED]> writes:
> what's the best approach to write C(++)-extension code that has to
> create a python int from a C pointer and vice versa so that it works
> smoothly on 32 bit and 64 platforms (on which sizeof(int) !=
> sizeof(*void)) equally work (under unix,mac&wi
what's the best approach to write C(++)-extension code that has to create a
python int from a C pointer and vice versa so that it works smoothly on 32 bit
and 64 platforms (on which sizeof(int) != sizeof(*void)) equally work (under
unix,mac&windows and with gcc, vc and borland)?
Currently the rele
