Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!aplcen!unmvax!pprg.unm.edu!topgun.dspo.gov!lanl!cmcl2!phri!marob!daveh
From: daveh@marob.masa.com (Dave Hammond)
Newsgroups: comp.lang.c
Subject: Re: time() warp.
Message-ID: <252CE46B.19C6@marob.masa.com>
Date: 6 Oct 89 17:44:10 GMT
Sender: daveh@marob.masa.com
Reply-To: daveh@marob.masa.com (Dave Hammond)
Organization: ESCC, New York City
Lines: 16

In article <252BFD80.194C@marob.masa.com> I wrote about problems using
time().  The mysterious clock problems turned out to be simply a matter
of a particular routine "assuming" that a standard header had properly
declared time(), when in fact that was not so.  The clock "flip-flop"
effect was the result of taking the time() value as a 32-bit quantity in
some places and a 16-bit quantity in others.

I apologize to the net for wasting bandwidth with this problem, as a
simple "linting" would have pointed me in the right direction.

My thanks to Tim Olson (tim@amd.com) for replying so quickly and
pointing out what should have been obvious.

--
Dave Hammond
daveh@marob.masa.com