RetroSearch Browse

Wed Aug 16 01:33:12 CEST 2006 · http://mail.python.org/pipermail/python-dev/2006-August/068275.html

On Aug 15, 2006, at 7:06 PM, Guido van Rossum wrote:
>> There's no particular reason that a short int must be able to store
>> the entire range of C "long", so, as many bits can be stolen from it
>> as desired.
>
> There isn't? Actually a lot of APIs currently assumen that.

I thought we were talking about Py3k. *IF* the idea is to integrate  
both short/long ints into a single type, with only an internal  
distinction (which is what is being discussed), all those APIs are  
broken already. The particular internal division of the new int  
object between short and long doesn't matter. Which is all I was saying.

If combining all integers into a single type isn't actually desired,  
then neither my message nor Martin's is relevant.

James

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

Showing content from http://mail.python.org/pipermail/python-dev/2006-August/068275.html below:

[Python-Dev] Type of range object members