From: "nobu (Nobuyoshi Nakada)" <nobu@...>
Date: 2012-07-06T12:10:27+09:00
Subject: [ruby-core:46213] [ruby-trunk - Bug #6702] Date should be either required or not


Issue #6702 has been updated by nobu (Nobuyoshi Nakada).


drbrain (Eric Hodel) wrote:
> (As a trade-off, Date and DateTime give you a much larger range than a Time.)

"Date and DateTime *had given* ..."

In 1.9 or later, Time has arbitrary range and precision.
----------------------------------------
Bug #6702: Date should be either required or not
https://bugs.ruby-lang.org/issues/6702#change-27842

Author: rosenfeld (Rodrigo Rosenfeld Rosas)
Status: Closed
Priority: Low
Assignee: drbrain (Eric Hodel)
Category: lib
Target version: 1.9.3
ruby -v: ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]


Today I was trying to do some experiment with IRB: "Date.today" threw a NoMethodError.

But Date was defined: "defined? Date" == "constant".

If I explicitly required for "date" it worked, but this is pretty much weird. It would be better if either:

 - I got an undefined "Date" class instead
 - "date" was automatically required

The current state is pretty much misleading.

This also happens in JRuby, so I guess somehow this is an intended behavior, but it doesn't make any sense to me.


-- 
http://bugs.ruby-lang.org/