Message 124839 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	belopolsky
Recipients	Rhamphoryncus, amaury.forgeotdarc, belopolsky, doerwalter, eric.smith, ezio.melotti, lemburg, loewis, pitrou, rhettinger, stutzbach, vstinner
Date	2010-12-29.01:25:41
SpamBayes Score	1.1773975e-08
Marked as misclassified	No
Message-id	<AANLkTi=KcpEbb4FD5M0xmF45Khtbfr=JzAUGLP13W41=@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: .. > * this version should be slightly faster and is also easier to read: > > #define Py_UCS4_READ_CODE_POINT(ptr, end) \ .. > Py_UNICODE_JOIN_SURROGATES((ptr)++, (ptr)++) : \ .. > I haven't tested it, but you get the idea. I don't think C guarantees the order of evaluation of the operands in bitwise expressions such as the expansion of the JOIN_SURROGATES macro.

On Sat, Nov 27, 2010 at 5:03 PM, Marc-Andre Lemburg
<report@bugs.python.org> wrote:
..
>  * this version should be slightly faster and is also easier to read:
>
> #define Py_UCS4_READ_CODE_POINT(ptr, end) \
..
>      Py_UNICODE_JOIN_SURROGATES((ptr)++, (ptr)++) : \
..
>   I haven't tested it, but you get the idea.

I don't think C guarantees the order of evaluation of the operands in
bitwise expressions such as the expansion of the JOIN_SURROGATES
macro.

History
Date	User	Action	Args
2010-12-29 01:25:44	belopolsky	set	recipients: + belopolsky, lemburg, loewis, doerwalter, rhettinger, amaury.forgeotdarc, Rhamphoryncus, pitrou, vstinner, eric.smith, stutzbach, ezio.melotti
2010-12-29 01:25:41	belopolsky	link	issue10542 messages
2010-12-29 01:25:41	belopolsky	create