Message105321
In Unicode-agnostic mode, instead of leaving Py_UNICODE, PyUnicodeObject, and many functions undefined, I wonder if it would be sufficient to declare Py_UNICODE like this:
struct PY_UNICODE_TYPE;
typedef struct PY_UNICODE_TYPE Py_UNICODE;
That would allow extensions to pass opaque Py_UNICODE pointers around, but not allow them to dereference the pointers nor evaluate sizeof(Py_UNICODE).
That would make PyUnicodeObject safe, as well as PyUnicode_Encode* and several other functions (anything that doesn't manipulate individual characters, basically). |
|
Date |
User |
Action |
Args |
2010-05-08 17:50:24 | stutzbach | set | recipients:
+ stutzbach, lemburg, gvanrossum, loewis, zooko, scoder, vstinner, r.david.murray |
2010-05-08 17:50:24 | stutzbach | set | messageid: <1273341024.37.0.0671421629743.issue8654@psf.upfronthosting.co.za> |
2010-05-08 17:50:21 | stutzbach | link | issue8654 messages |
2010-05-08 17:50:20 | stutzbach | create | |
|