[issue10542] Py_UNICODE_NEXT and other macros for surrogates
Tom Christiansen
report at bugs.python.org
Tue Aug 16 13:44:15 CEST 2011
Tom Christiansen <tchrist at perl.com> added the comment:
Antoine Pitrou <report at bugs.python.org> wrote
on Tue, 16 Aug 2011 09:18:46 -0000:
>> I think the 4 macros:
>> #define _Py_UNICODE_ISSURROGATE
>> #define _Py_UNICODE_ISHIGHSURROGATE
>> #define _Py_UNICODE_ISLOWSURROGATE
>> #define _Py_UNICODE_JOIN_SURROGATES
>> are quite straightforward and can avoid using the trailing _.
> I don't want to bikeshed, but can we have proper consistent word separation?
> _Py_UNICODE_IS_HIGH_SURROGATE, not _Py_UNICODE_ISHIGHSURROGATE
> (etc.)
Oh good, I thought it was only me whohadtroublereadingthose. :)
--tom
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10542>
_______________________________________
More information about the Python-bugs-list
mailing list