Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg <rep...@bugs.python.org> wrote: .. > * same for the Py_UNICODE_NEXT() macro, i.e. Py_UCS4_NEXT() > > * in order to make the macro easier to understand, please rename it to > Py_UCS4_READ_CODE_POINT(); that's a little more typing, but still > a lot less than without the macro :-) I am not sure Py_UCS4_ prefix is right here. (I agree on *SURROGATE* methods.) The point of Py_UNICODE_NEXT(ptr, end) is that the pointers ptr and end are Py_UNICODE* and the macro expands to *p++ on wide builds. Maybe Py_UNICODE_NEXT_USC4? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10542> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
