Subject: Re: mktime(3) fails to convert a time in the "spring forward gap"
To: Bill Studenmund <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 10/09/2002 14:33:40
[ On Wednesday, October 9, 2002 at 11:10:03 (-0700), Bill Studenmund wrote: ]
> Subject: Re: mktime(3) fails to convert a time in the "spring forward gap"
> On Thu, 10 Oct 2002 firstname.lastname@example.org wrote:
> > >> > It seems NetBSD's (and FreeBSD, at least 4.7-RC's) mktime(3) fails to
> > >> > convert a time in the "spring forward gap".
> > FWIW, configure.in shipped with the latest GNU tar also checks
> > this and rejects NetBSD mktime(3).
> Is there any standards input on this?
I quoted all I could find on them in my last post to this thread.
> Because it seems to me that what our
> mktime is doing is perfectly fine. Those times don't exist on the wall
> clock, so we shouldn't accept them. Just like we say don't accept
Those wall clock times only don't exist in certain timezones, and as I
tried to explain in my previous post an application which tries to
calculate offsets using mktime() shouldn't fail in Toronto and yet work
in Regina even if it's run at the same local time of day on some certain
I have not yet looked at GNU's libc (which has apparently had a fix for
the past four years or so), but I suspect the solution they use is to
simply convert inter-gap times to end/beginning-of-gap times.
Greg A. Woods
+1 416 218-0098; <email@example.com>; <firstname.lastname@example.org>
Planix, Inc. <email@example.com>; VE3TCP; Secrets of the Weird <firstname.lastname@example.org>