Message122568
| Author |
belopolsky |
| Recipients |
Rhamphoryncus, amaury.forgeotdarc, belopolsky, eric.smith, ezio.melotti, lemburg, loewis, pitrou, rhettinger, vstinner |
| Date |
2010年11月27日.22:19:34 |
| SpamBayes Score |
0.00016942421 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTinOHNDpk5qAUqDL16p_cxMAcFM0FvEL45ZHYEA0@mail.gmail.com> |
| In-reply-to |
<1290895400.38.0.59035357378.issue10542@psf.upfronthosting.co.za> |
| Content |
On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg
<report@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? |
|