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

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

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

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

On Thu, 6 Jul 2000, Bill Tutt wrote:

> 
> 
> Its definately for at least 32 bits. 
> Having a 32 bit specific type lets me not worry about all the issues
> relating to:
> What happens if sizeof(int) | sizeof(long) > 32 bits and I failed to 
> compensate for that somehow.
> 
> Now, the code that I changed to use the typedef might not care about this,
> but other code using the typedef might. Just color me a paranoid SOB. :)
> I'd rather always have a 32 bit type for something I know will always
> require just 32 bits.
> 

In any event, having the typedef is still useful since it clarifies the
meaning behind the code.

Bill

• Previous message: [Python-Dev] RE: [Patches] [Patch #100745] Fix PR #384, fixes UTF-8 en/decode
• 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