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: .. [I'll respond to skipped when I update the patch] > In any case, we should clearly document where these macros are used and > warn about the implications of using them in the wrong places. It may be best to start with _Py_UCS2_READ_CODE_POINT() (BTW, I like the name because it naturally lead to Py_UCS2_WRITE_CODE_POINT() counterpart.) The leading underscore will probably not stop early adopters from using it and we may get some user feedback if they ask to make these macros public. ---------- _______________________________________ 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
