[Python-Dev] Py_ssize_t output parameters (Was: [Python-checkins] r41971 ...) (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Tue Jan 10 20:17:19 CET 2006
- Previous message: [Python-Dev] PyThreadState_Delete vs PyThreadState_DeleteCurrent
- Next message: [Python-Dev] Py_ssize_t output parameters (Was: [Python-checkins] r41971 ...)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
M.-A. Lemburg wrote:
I don't believe the change is major. It only affects a few extensions, and for these, it is only a minor change. A single line of changing will be enough.
This is true for all the changes related to parameters passed by value. It is not true for output parameters. For these, the change will propagate into the extension and make quite a few changes necessary (for the same reason you have to change so many variables to Pyssizet).
For the output parameter, just the variable receiving the value needs to be changed, and you are done.
We should make it possible to have a simple recompile of old extensions continue to work with Python 2.5 (albeit without them supporting 64-bit indexes) and without introducing segfaults or buffer overflows that way.
I cannot see how this could reasonably achieved for arbitrary extension modules.
Regards, Martin
- Previous message: [Python-Dev] PyThreadState_Delete vs PyThreadState_DeleteCurrent
- Next message: [Python-Dev] Py_ssize_t output parameters (Was: [Python-checkins] r41971 ...)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]