-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 19 Mar 1998, Maarten Boekhold wrote:
> AFAIK tzset() is called automagically by all time-related libc routines
> when they detect it is not set yet (at least I think with Linux it is
> done this way. It's been a long time since I looked at that).
That would explain it then. I was just accessing the variables
directly, without any intervening calls.
It's a moot point, anyway. I put explicit calls in to the
startup, and it made no difference in the result. It's likely to
be a 32/64 bit issue somewhere that I haven't located yet. It
really shouldn't be that hard to track down. Since the output is
different from the input by a consistance amount (19 years +- a
few days) it can only be in one of 4 places, AFAIK: parsing
input, storing value, retrieving value, or generating output. My
bet is on the retrieve phase, but we'll see.
- --
Dwayne Bailey + WHAT is your name? Sir Galahad
MIKA Systems, Bingham Farms, MI + WHAT is your quest? I Seek the Holy Grail
dwayne@mika.com + What is your favorite color?
http://www.mika.com/~dwayne + Blue ... no, Yelloooooooooooooooooow
finger dwayne@mika20.mika.com for PGP Public Key
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQB1AwUBNRE5eqA2uleK7maRAQGqPQMAgajIzCAK8cBRmqCHw83mVyI8i5YI7yo4
j0jhJXG3vEauLST0B+6ompKw0+KQvRoOfgFWOoyqelZ08zo6qCBrJJmuAbGSM1/b
EbBtsORCpSymqaeDIIPHoPdaq+jG9c8e
=BiGQ
-----END PGP SIGNATURE-----