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 belopolsky, dmalcolm, docs@python, eric.araujo, terry.reedy, vstinner
Date 2010-12-08.22:55:09
SpamBayes Score 7.709056e-06
Marked as misclassified No
Message-id <1291848911.44.0.756446519525.issue9738@psf.upfronthosting.co.za>
In-reply-to
Content
> A (probably crazy) idea that just occurred to me:
>  typedef char utf8_bytes;
>  typedef char iso8859_1_bytes;
>  typedef char fsenc_bytes;

I like it!  Let's see how far we can get without iso8859_1_bytes, though.  (It is likely to be locale_bytes anyways.)  There are a few places where we'll need ascii_bytes.

The added benefit is that we can make these typedefs unsigned char and avoid char signness being ambiguous.  We will also need to give the typedefs the Py_ prefix.

And an obligatory bikesheding comment: if we typedef char, we should use singular form.  Or we can typedef char* Py_utf8_bytes.
History
Date User Action Args
2010-12-08 22:55:11belopolskysetrecipients: + belopolsky, terry.reedy, vstinner, eric.araujo, dmalcolm, docs@python
2010-12-08 22:55:11belopolskysetmessageid: <1291848911.44.0.756446519525.issue9738@psf.upfronthosting.co.za>
2010-12-08 22:55:09belopolskylinkissue9738 messages
2010-12-08 22:55:09belopolskycreate