On Thu, Oct 3, 2013 at 3:36 AM, Lester Caine <lester@lsces.co.uk> wrote:
Of cause while the number of people affected by 'pre-history' dates with time is not so great, nowadays the 2038 rollover has to be taken seriously, and anybody still stuck with software affected by it needs to be
I'd just like to point out that there are already actively traded government bonds issued by the Kingdom of Morocco that mature in 2042 (12/11/2042 to be exact). The financial sector actively works with dates > 2037 all the time because bonds have very long time horizons.
I've already run into bugs interfacing tzdata to JS interpreters where passing a date+midnight > 2037 will result in the (date - 1 day) due to the tzdata code believing there is no DST, but the script interpreter believes there is DST because the interpreter "maps" years > 2037 to equivalent prior years where there is data (which is broken, anyway -- fixed in ES6 spec, but just pointing out real-world encounters here).