> Is it ok to add the following: > * a Py_off_t type which is typedef'd to either Py_LONG_LONG (Windows) or > off_t > (others) > * three C API functions: PyNumber_AsOff_t, PyLong_AsOff_t, PyLong_FromOff_t > * an additional type code for PyArg_ParseTuple and friends; I suggest 'N' > since > 'n' currently means Py_ssize_t, and a Py_off_t should always be at least as > wide > as a Py_ssize_t > ?
-1. How many functions actually require that type? > (the motivation is systems where Py_ssize_t is 32-bits wide, but large file > support makes off_t 64 bits wide) For argument parsing, you should use "long long" if SIZEOF_OFF_T is 8 and long long is supported, and then assign to off_t as appropriate. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
