Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!apple!bionet!agate!labrea!decwrl!sun!pitstop!sundc!seismo!uunet!steinmetz!davidsen
From: davidsen@steinmetz.ge.com (William E. Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: struct tm -> time_t converter wanted
Keywords: C library, time
Message-ID: <12418@steinmetz.ge.com>
Date: 25 Oct 88 19:50:25 GMT
References: <442@grand.UUCP> <8700@smoke.BRL.MIL> <6964@cdis-1.uucp> <8716@smoke.BRL.MIL>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 16

In article <8716@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:

| Some of us believe that well before 2038 the 64-bit integer will be in
| wide use.

In fifty years 64 bit ints will be standard in digital watches. However,
changing the epoch or going to 64 bits would break existing programs. I
don't expect that my programs or I will live to see it, so I guess I'll
postpone worrying about it.

Not in any way to say that the problem doesn't exist, it's just not what
I consider *pressing*.
-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me