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

Showing content from https://mail.python.org/pipermail/python-dev/2002-October/029276.html below:

[Python-Dev] Unclear on the way forward with unsigned integers

• Previous message: [Python-Dev] Unclear on the way forward with unsigned integers
• Next message: [Python-Dev] Unclear on the way forward with unsigned integers
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Tim Peters <tim.one@comcast.net> writes:

> The result of that is also currently platform-dependent, so you need to say
> what you mean in a platform-independent way.  It's likely that you meant
> 
>     hex(-1 & 0xffffffffL)
> 
> or, more directly,
> 
>     hex(0xffffffffL)
> 
> but that someone on a 64-bit box meant something other than that.

Alternatively, if he really means what hex(-1) will mean in the
future, he should really write hex(-1L), or, if -1 is a variable,
hex(long(-1)).

Regards,
Martin

• Previous message: [Python-Dev] Unclear on the way forward with unsigned integers
• Next message: [Python-Dev] Unclear on the way forward with unsigned integers
• 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