
> > > How about having some #if BROKEN_TIMEZONE_DATABASE code which uses both
> > > mktime() and localtime() to derive the correct time zone? That is, call
> > > mktime to get a time_t, then call localtime() to get the time zone info,
> > > but only on platforms which do not get a complete result from just the
> > > call to mktime(). In fact, we *could* check for tm->tm_isdst coming back
> > > "-1" for every platform, then call localtime() to make a last stab at
> > > getting a good value.
> > How would we construct a valid time_t from the struct tm 
> without mktime?
> 
> If I understand the info you have given previously, it should be
> possible to get a valid tm->tm_isdst by the following 
> sequence of calls:
> 
> // call mktime() which might return a "-1" for DST
> time = mktime(tm);
> // time is now a correct GMT time

Unfortunately the returned time is -1 for all dates before 1970 
(on AIX and, as I understood, IRIX) :-( 
(can you send someone from IBM, that I can shout at, to releive my anger)

Andreas

Fri, 12 Jan 2001 09:40:20 +0100
Zeugswetter Andreas SB  <ZeugswetterA@wien.spardat.at>
AW: AW: AW: AW: Re: tinterval - operator problems on AIX