[#66678] [ruby-trunk - Feature #10481] Add "if" and "unless" clauses to rescue statements — alex@...
Issue #10481 has been updated by Alex Boyd.
3 messages
2014/12/04
[#66762] Re: [ruby-changes:36667] normal:r48748 (trunk): struct: avoid all O(n) behavior on access — Tanaka Akira <akr@...>
2014-12-10 0:44 GMT+09:00 normal <ko1@atdot.net>:
3 messages
2014/12/10
[#66851] [ruby-trunk - Feature #10585] struct: speedup struct.attr = v for first 10 attributes and struct[:attr] for big structs — funny.falcon@...
Issue #10585 has been updated by Yura Sokolov.
3 messages
2014/12/15
[#67126] Ruby 2.2.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 2.2.0.
8 messages
2014/12/25
[#67128] Re: Ruby 2.2.0 Released
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2014/12/25
I can't install it in any of our Ubuntu servers using rbenv:
[#67129] Re: Ruby 2.2.0 Released
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/12/25
> I can't install it in any of our Ubuntu servers using rbenv:
[ruby-core:66998] [ruby-trunk - Bug #10588] [Rejected] Invalid Dates
From:
akr@...
Date:
2014-12-20 09:26:31 UTC
List:
ruby-core #66998
Issue #10588 has been updated by Akira Tanaka.
Status changed from Open to Rejected
It is not good idea to restrict current methods to reject invalid dates and times.
I tried to verify invalid time using round trip test once.
(ruby-core:14517, ruby-dev:33058, r14765, r15203)
But it caused bigger problems over benefits.
Invalid date/time is difficult to determine.
It is almost impossible by application because it depends various factors:
Month, leap year, summer time, leap seconds, time zone definition change.
Sometimes application needs a Time object near given year/month/day/hour/minute/second.
It is very difficult to do using the restricted methods.
So, methods only accept valid dates are less useful than current methods.
----------------------------------------
Bug #10588: Invalid Dates
https://bugs.ruby-lang.org/issues/10588#change-50527
* Author: Imran ""
* Status: Rejected
* Priority: Normal
* Assignee:
* Category:
* Target version:
* ruby -v: 2.0.0-p481
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
I was in the process of implementing a date-routine, which could prevent possible out-of-range/invalid date values.
The interpreter, rightfully, threw an out-of range error, when I tried any of the following:
puts Time.mktime 2014, 13, 32
puts Time.mktime 2014, 13, 32
No surprises there. However, when I tried:
puts Time.mktime 2014, 11, 31
The interpreter, happily produced: 2014-12-01.
A little intrigued, I went ahead and tried the following routine:
1.upto(12){|month| puts Time.mktime 2014, month, 31}
Result:
2014-01-31 ok
2014-03-03 ???
2014-03-31 ok
2014-05-01 ???
2014-05-31 ok
2014-07-01 ???
2014-07-31 ok
2014-08-31 ok
2014-10-01 ???
2014-10-31 ok
2014-12-01 ???
2014-12-31 ok
I hope, I've been able to describe this issue adequately.
Thanks Matz & all the contributors for bringing this wonderful tool to us.
Regards.
--
https://bugs.ruby-lang.org/