[#6363] Re: rescue clause affecting IO loop behavior — ts <decoux@...>

>>>>> "D" == David Alan Black <dblack@candle.superlink.net> writes:

17 messages 2000/11/14
[#6367] Re: rescue clause affecting IO loop behavior — David Alan Black <dblack@...> 2000/11/14

Hello again --

[#6582] best way to interleaf arrays? — David Alan Black <dblack@...>

Hello --

15 messages 2000/11/26

[#6646] RE: Array Intersect (&) question — Aleksi Niemel<aleksi.niemela@...>

Ross asked something about widely known and largely ignored language (on

23 messages 2000/11/29
[#6652] RE: Array Intersect (&) question — rpmohn@... (Ross Mohn) 2000/11/29

aleksi.niemela@cinnober.com (Aleksi Niemel) wrote in

[#6723] Re: Array Intersect (&) question — Mathieu Bouchard <matju@...> 2000/12/01

> >Use a hash. Here's code to do both and more. It assumes that

[#6656] printing/accessing arrays and hashes — raja@... (Raja S.)

I'm coming to Ruby with a Python & Common Lisp background.

24 messages 2000/11/30

[ruby-talk:6139] Re: More Date/Time inconsistencies

From: "Brian F. Feldman" <green@...>
Date: 2000-11-07 19:44:37 UTC
List: ruby-talk #6139
matz@zetabits.com (Yukihiro Matsumoto) wrote:

> This is exactly what I meant by urban legend.  You find description
> about 61st second everywhere, but no solid evidence of its existence.
> 
> 							matz.

From FreeBSD's src/lib/libc/stdtime/localtime.c, from the call path such as
localtime() -> localsub() -> timesub():

        /*
        ** A positive leap second requires a special
        ** representation.  This uses "... ??:59:60" et seq.
        */
        tmp->tm_sec = (int) (rem % SECSPERMIN) + hit;

"hit" is the leap seconds, of course.  The documentation says:

           int tm_sec;     /* seconds (0 - 60) */

Hope this helps.

--
 Brian Fundakowski Feldman           \  FreeBSD: The Power to Serve!  /
 green@FreeBSD.org                    `------------------------------'



In This Thread

Prev Next