On Fri, Oct 1, 2010 at 2:12 PM, Jonathan Link <jonathan.l...@gmail.com> wrote: > What about the 2038 problem?
That's a somewhat different beast. Y2K is mainly a human factors problem, as it's humans who like two-digit years, not computers. (Contrary to popular belief, data storage capacity was *not* the big contributor to Y2K.) 2038 is a straight technology capacity limit. As far as Y2038 goes... conventional thinking is that everyone will have moved to a 64-bit signed integer before it becomes a problem. Per the spec, time_t is an opaque data structure, so properly-written code won't notice. [pause for laughter] But even code that does math directly on time_t prolly won't care, since the math should be the same. If you need binary compatibility with old data structures, though... well, sucks to be you. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
