Thomas Wouters wrote: > And so I could. test_banana.CananaTestCase.testCrashNegativeLong > crashes, because it calls PyString_AsStringAndSize() with an int-ptr as > second argument (an adjacent ptr variable becomes garbage.) That's > certainly a problem with the Py_ssize_t change. Martin, aren't all > output variables (or ptr-variables, rather) supposed to be controlled by > the 'PY_SSIZE_T_CLEAN' #define? People aren't going to notice their > compiler warnings; I know I didn't :)
No: this is the discussion I had with MAL. You have to watch for compiler warnings talking about incorrect pointer types. These days, you can apply Fredrik's checker to find out that you are using functions that output Py_ssize_t. Ignoring the warning might cause crashes on 64-bit machines. On 32-bit machines, there should be any negative consequence. 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
