John Ralls <[email protected]> writes:
>> This is the "year 2037" problem, where 32-bit unsigned time rolls over.
>> However there is also a "Year 2106" problem, which is where 32-bit
>> unsigned time rolls over. I think there *are* some systems where it's
>> unsigned, but still 32 bits. Or at least there are apps where that is
>> the case.
> It's actually the "2038 problem", as a signed 32-bit time_t overflows
> at 03:14:07 2038-01-19.
2037.. 2038.... (had I done the simple math 9 days ago I would've
gotten the year right -- I didn't remember the exact date. Shame on me)
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[email protected] PGP key available
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
