5 ms·

The scary thing is that integer overflows are considered rare so unlike things like null-pointer dereference no one really checks for them (heck, it seems impra

by mikevm 13y ago

The scary thing is that integer overflows are considered rare so unlike things like null-pointer dereference no one really checks for them (heck, it seems impractical checking for it). In this case, how should they defend against an overflow? Impose an arbitrary limit on gold?

Jabbles 13y ago
Use 64 bit integers everywhere.
- TwoBit 13y ago
  Why not 128 bit integers.
maaku 13y ago
Check for them. There's no lazy way out.
wtetzner 13y ago
Use arbitrary precision integers. It's hard to imaging the performance would be noticeably impacted for storing the amount of gold someone has.