[MAL] > Note that Unicode code which needs enough bits to hold a UCS4 > value should always use the Py_UCS4 type (see unicodeobject.h)... > any changes needed to assure the 32-bit nature should then > be made to the Py_UCS4 typedef. That's fine. The Py_UCS4 typedef should in turn be defined by direct reference to a C9X-derived typedef from pyport.h: the latter is where 32-bitness "should be" defined. Then the only changes ever needed will be to pyport.h (where people will *expect* such changes to get made).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4