Hacker Read

ender7 | karma 5043 | avg karma 11.59 · 2012-10-09 01:04:30

I don't see how this is any different from overflowing an int32 in any other programming language. Sure, with an int, x != x + 1 even after an overflow, but your program is still going to crash when it tries to bill you for negative two billion widgets.

If you're dancing on the edge of the limits of numerical representation then you need to write code to protect against bad things. If you don't write said code, your program is going to fail to work correctly, no matter what language you use.

reply

mietek | karma 2130 | avg karma 3.32 · 2012-10-09 07:13:07+00:00

The difference is, in other programming languages you usually have a choice to use an integer number type.

hythloday | karma 2159 | avg karma 4.73 · 2012-10-09 11:01:32+00:00

"Overflowing an int" is something that I worry about when I'm thinking in terms of memory layout of data. I shouldn't have to worry about it when working at a higher level of abstraction. Python handles this correctly:

  >>> int('0x7fffffff', 16)
  2147483647
  >>> int('0x7fffffff', 16) + 1
  2147483648L