Re: date overflow in year 2038

2009-02-22 Thread Dr. David Alan Gilbert
* James Youngman (j...@gnu.org) wrote: > On Sat, Feb 14, 2009 at 3:45 AM, David M. Dowdle > wrote: > > > > I'd rank this as low priority, but people doing things like 30 year mortages > > will be hitting this already. > > > > Mortgage calculations probably shouldn't be using time_t anyway; use >

Re: date overflow in year 2038

2009-02-20 Thread James Youngman
On Sat, Feb 14, 2009 at 3:45 AM, David M. Dowdle wrote: > > I'd rank this as low priority, but people doing things like 30 year mortages > will be hitting this already. > Mortgage calculations probably shouldn't be using time_t anyway; use of time_t for future calculations assumes that we already

Re: date overflow in year 2038

2009-02-14 Thread Dr. David Alan Gilbert
* Eric Blake (e...@byu.net) wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to David M. Dowdle on 2/13/2009 8:45 PM: > > clouded:~> date -d "Fri Jan 19 03:14:08 UTC 2038" +%s > > date: invalid date `Fri Jan 19 03:14:08 UTC 2038' > > clouded:~> > > > > 03:14:07 is apparently

Re: date overflow in year 2038

2009-02-13 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to David M. Dowdle on 2/13/2009 8:45 PM: > clouded:~> date -d "Fri Jan 19 03:14:08 UTC 2038" +%s > date: invalid date `Fri Jan 19 03:14:08 UTC 2038' > clouded:~> > > 03:14:07 is apparently when 32bit time_t hits MAXINT Yep, and that's why m

date overflow in year 2038

2009-02-13 Thread David M. Dowdle
clouded:~> date -d "Fri Jan 19 03:14:06 UTC 2038" +%s 2147483646 clouded:~> date -d "Fri Jan 19 03:14:07 UTC 2038" +%s 2147483647 clouded:~> date -d "Fri Jan 19 03:14:08 UTC 2038" +%s date: invalid date `Fri Jan 19 03:14:08 UTC 2038' clouded:~> clouded:~> date --version date (GNU coreutils) 6.