Once upon a time, Robert Moskowitz <r...@htt-consult.com> said: > On 01/20/2014 06:47 AM, Frank Murphy wrote: > >On Mon, 20 Jan 2014 06:45:54 -0800 > >Robert Moskowitz <r...@htt-consult.com> wrote: > > > >>>The day will come when all OS providers, > >>>will give cutoff for 32bit hardware\code > >>Well that is a given by 2026.... > >> > >>:) > >> > >> > >Amazing what a guess will get ya, > >jail or laurels. :) > > The death, so to speak, for the 32 bit time field. Yes, it is > handle rather well now in software in preparation for that day, but > there is still plenty of bad stuff that will make all the planning > for y2k look like play stuff.
Oh, was that what was supposed to be? That's not until 2038 (for 32 bit signed int and epoch = 1970-01-01 00:00:00). I really doubt that it will be that big of a deal. Most databases use actual date fields, not time_t (since time_t already doesn't cover many interesting dates). Not all OSes use the same epoch either, so this is mostly a Unix problem, and most current Unix systems already handle a larger time_t (if somebody is still trying to make SunOS 4 or SCO run in 2038, time_t will be the least of their problems). -- Chris Adams <li...@cmadams.net> -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
