Hmm, I always thought what happened on integer overflow was purely a hardware dependent thing. (which I always hoped rolls over or segfaults on the majority of architectures lol)
Quote:
Originally Posted by BSDfan666
I suspect that when the decision was made to use a signed 32-bit integer for time_t, larger types were either unavailable or inefficient..
|
I would reckon at the time, 32-bit integers would have been like picking a 64-bit integer today: be happy if you have it available, but don't bet on it to be a chorts.
__________________
My
Journal
Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''.