➜

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, eric.smith, ezio.melotti, lemburg, loewis, pitrou, rhettinger, vstinner
Date 2010-11-27.22:14:05
SpamBayes Score 8.786252e-05
Marked as misclassified No
Message-id <AANLkTimDQLg2fbaQ9_1-SHPsrdNcb=hxWxBQKOp8=jPp@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:
.. [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.
History
Date User Action Args
2010-11-27 22:14:08belopolskysetrecipients: + belopolsky, lemburg, loewis, rhettinger, amaury.forgeotdarc, Rhamphoryncus, pitrou, vstinner, eric.smith, ezio.melotti
2010-11-27 22:14:05belopolskylinkissue10542 messages
2010-11-27 22:14:05belopolskycreate