[ruby-talk:6030] Re: Ref.: Re: Time.local bug?

On Fri, 3 Nov 2000, Dave Thomas wrote:

> > Also, ISO 8601, allows hour '24' as a equivalent to '00' and I have
> > read somewhere that the may be a second '61' some times, but I
> > haven't found that in any official document, so there's nothing
> > solid in that...
> 
> Well, seconds run from 0 to 60, so Ruby does allow you to have 61
> second minutes. These are leap minutes.
> 
>  Time.local 59, 49, 5, 3, 11, 2000, 5, 308, false, "CST"# => Fri Nov 03 05:49:59 CST 2000
>  Time.local 60, 49, 5, 3, 11, 2000, 5, 308, false, "CST"# => Fri Nov 03 05:50:00 CST 2000

Doesn't this paragraph from RFC 1305:

For the most precise coordination and timestamping of events since 1972,
it is necessary to know when leap
seconds are implemented in UTC and how the seconds are numbered. As
specified in CCIR Report 517,
which is reproduced in [BLA74], a leap second is inserted following second
23:59:59 on the last day of June or
December and becomes second 23:59:60 of that day. A leap second would be
deleted by omitting second
23:59:59 on one of these days, although this has never happened. Leap
seconds were inserted prior to 1
January 1991 on the occasions listed in Table 8<$&tab8> (courtesy
U.S. Naval Observatory). Published
IBWM corrections consist not only of leap seconds, which result in step
discontinuities relative to TAI, but
100-ms UT1 adjustments called DUT1, which provide increased accuracy for
navigation and space science. 

suggest that that is worng?  The time yielded should be 03 05:49:60, I
think.  I'm no expert on this topic, though.
> 
> Regards
> 
> 
> Dave

	Hugh