Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-July/005621.html below:

[Patches] [Patch #100745] Fix PR #384, fixes UTF-8 en/decode

• Previous message: [Python-Dev] Collection of typedefs for integral types
• Next message: [Python-Dev] RE: [Patches] [Patch #100745] Fix PR #384, fixes UTF-8 en/decode
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[moved from patches to python-dev]

[Bill Tutt]
> Code currently in unicodeobject.c needs to do 32-bit arithmetic in
> order to work. Additionally, UCS-4 characters (aka UTF-16 surrogate
> characters) require 32 bits to represent the true unicode code point of a
> surrogate pair.

But is the requirement really for *exactly* 32 bits, or for *at least* 32
bits?  The problem isn't with feebler machines, it's with higher-end ones:
on some Python platforms, even sizeof(short) == 8.  As is, your patch will
prevent Python from compiling on those.

• Previous message: [Python-Dev] Collection of typedefs for integral types
• Next message: [Python-Dev] RE: [Patches] [Patch #100745] Fix PR #384, fixes UTF-8 en/decode
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4