[Python-Dev] Deprecation warning on integer shifts and such
Wed, 14 Aug 2002 11:29:42 +0200
On Wednesday, August 14, 2002, at 04:39 , Guido van Rossum wrote:
> How about the following counterproposal. This also changes some of
> the other format codes to be a little more regular.
> Code C type Range check
> b unsigned char 0..UCHAR_MAX
> B unsigned char none **
> h unsigned short 0..USHRT_MAX
> H unsigned short none **
> i int INT_MIN..INT_MAX
> I * unsigned int 0..UINT_MAX
> l long LONG_MIN..LONG_MAX
> k * unsigned long none
> L long long LLONG_MIN..LLONG_MAX
> K * unsigned long long none
> * New format codes.
> ** Changed from previous "range-and-a-half" to "none"; the
> range-and-a-half checking wasn't particularly useful.
Fine with me.
My only reason for suggesting the uint32_t and friends was because I was
under the impression that you were unhappy with "unsigned long" having
a different size on different platforms. I'm perfectly happy with
- Jack Jansen <Jack.Jansen@oratrix.com>
- If I can't dance I don't want to be part of your revolution -- Emma