From: akr@... Date: 2014-12-20T09:26:31+00:00 Subject: [ruby-core:66998] [ruby-trunk - Bug #10588] [Rejected] Invalid Dates 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/