[#29911] [Bug #3231] Digest Does Not Build — Charlie Savage <redmine@...>

Bug #3231: Digest Does Not Build

19 messages 2010/05/01

[#29920] [Feature #3232] Loops (while/until) should return last statement value if any, like if/unless — Benoit Daloze <redmine@...>

Feature #3232: Loops (while/until) should return last statement value if any, like if/unless

9 messages 2010/05/01

[#29997] years in Time.utc — Xavier Noria <fxn@...>

Does anyone have a precise statement about the years supported by

13 messages 2010/05/04

[#30010] [Bug #3248] extension 'tk' is finding tclConfig.sh and tkConfig.sh incorrectly — Luis Lavena <redmine@...>

Bug #3248: extension 'tk' is finding tclConfig.sh and tkConfig.sh incorrectly

9 messages 2010/05/05

[#30226] [Bug #3288] Segmentation fault - activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:88 — Szymon Jeż <redmine@...>

Bug #3288: Segmentation fault - activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:88

10 messages 2010/05/13

[#30358] tk doesn't startup well in doze — Roger Pack <rogerdpack2@...>

Currently with 1.9.x and tk 8.5,the following occurs

12 messages 2010/05/22

[ruby-core:30031] Re: years in Time.utc

From: Benoit Daloze <eregontp@...>
Date: 2010-05-05 19:46:45 UTC
List: ruby-core #30031
Hi,

> Ruby 1.9.2 has changed the internal representation, it looks like it
> uses a Ruby integer object internally, so the range expands to
> bignums. So I think the answer for 1.9.2 is that you can use any
> integer value for year.
> --
> Rick DeNatale

Just playing in irb, remembering that 1.9.2 is supposed to manage any
Time and got a weird problem:

irb for ruby-1.9.2-r27602
> Time.new -20000
=> -20000-01-01 00:00:00 +0000  # immediate
> Time.new -20001
=> -20001-01-01 00:00:00 +0000  # immediate
> Time.new -20002 # Seems to be an infinite loop, it takes 100% during at least 60s
^C^C^CKilled

Any idea why does it get stuck like that ?

Regards,
B.D.

In This Thread