Message-ID:	<3A5D0A33.1182@earthlink.net>
From:	Joe Wright <joewwright AT earthlink DOT net>
X-Mailer:	Mozilla 3.03Gold (Win95; I)
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	It's about time()
Lines:	19
Date:	Thu, 11 Jan 2001 01:47:54 GMT
NNTP-Posting-Host:	63.215.156.56
X-Complaints-To:	abuse AT earthlink DOT net
X-Trace:	newsread2.prod.itd.earthlink.net 979177674 63.215.156.56 (Wed, 10 Jan 2001 17:47:54 PST)
NNTP-Posting-Date:	Wed, 10 Jan 2001 17:47:54 PST
Organization:	EarthLink Inc. -- http://www.EarthLink.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I installed djgpp v2.0 'out of the box' several years ago now and it has
worked perfectly for me, and still does.  But 'time' is one of those
things I really don't have a handle on.  The business about time zones
and daylight time.  Both localtime() and gmtime() return the time of the
system clock and tm_zone says "GMT" and tm_gmtoff is 0.

Is there some setup thing such that localtime() reports the system
clock, tm_zone is "EST" and gmtime() is five hours later?

Do you know why...
- all the time functions take pointers to time_t vars rather than
values.
- tm_mday is the only rel-1 value in struct tm.  All others are rel-0.

Curious.
-- 
Joe Wright                          mailto:joewwright AT earthlink DOT net
"Everything should be made as simple as possible, but not simpler."
                    --- Albert Einstein ---

- Raw text -