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

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

[Python-Dev] issues with int/long on 64bit platforms

• Previous message: [Python-Dev] issues with int/long on 64bit platforms - eg stringobject (PR#306)
• Next message: [Python-Dev] issues with int/long on 64bit platforms - eg stringobject (PR#306)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I've just posted a simple patch to the patches list which
implements the idea I posted earlier:

Silent truncation still takes place, but in a somwhat more
natural way ;-) ...

                       /* Silently truncate to INT_MAX/INT_MIN to
                          make passing sys.maxint to 'i' parser
                          markers work on 64-bit platforms work just
                          like on 32-bit platforms. Overflow errors
                          are not raised. */
                       else if (ival > INT_MAX)
                               ival = INT_MAX;
                       else if (ival < INT_MIN)
                               ival = INT_MIN;
                       *p = ival;

-- 
Marc-Andre Lemburg
______________________________________________________________________
Business:                                      http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/

• Previous message: [Python-Dev] issues with int/long on 64bit platforms - eg stringobject (PR#306)
• Next message: [Python-Dev] issues with int/long on 64bit platforms - eg stringobject (PR#306)
• 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