[#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:6528] Re: Time Trouble

From: Niklas Backlund <d99-nba@...>
Date: 2000-11-22 19:41:38 UTC
List: ruby-talk #6528

On Thu, 23 Nov 2000, Hugh Sasse Staff Elec Eng wrote:

> > > Niklas Backlund <d99-nba@nada.kth.se> writes:
> > >
> > > >
> > > > Can someone please explain this result to me:
> > > >
> > > > irb(main):001:0> 1.upto(12) {|m| puts Time.local(2000, m, 1, 0, 0)}
> > > > Sat Jan 01 00:00:00 GMT+1:00 2000
> > > > Tue Feb 01 00:00:00 GMT+1:00 2000
> > > > Wed Mar 01 00:00:00 GMT+1:00 2000
> > > > Sat Apr 01 01:00:00 GMT+1:00 2000
> > > > Mon May 01 01:00:00 GMT+1:00 2000
> > > > Thu Jun 01 01:00:00 GMT+1:00 2000
> > > > Sat Jul 01 01:00:00 GMT+1:00 2000
> > > > Tue Aug 01 01:00:00 GMT+1:00 2000
> > > > Fri Sep 01 01:00:00 GMT+1:00 2000
> > > > Sun Oct 01 01:00:00 GMT+1:00 2000
> > > > Wed Nov 01 00:00:00 GMT+1:00 2000
> > > > Fri Dec 01 00:00:00 GMT+1:00 2000
>
> I think you are right: this is incorrect.  In the summer it should
> set the timezone to GMT+2:00, shouldn't it?  If it is taking account of
> Daylight Saving Time....

Yeah, if you want to create an object referring to something
that ocurred in the past, you shouldn't have to compensate an
hour (sometimes) to get it right, should you? I'd say there's
something fishy about this behaviour...

We should let the OS handle the Daylight Savings Time instead.

/Niklas



In This Thread