From: "kommen (Dieter Komendera)" <dieter@...>
Date: 2013-08-28T00:07:14+09:00
Subject: [ruby-core:56829] [ruby-trunk - Bug #6702] Date should be either	required or not


Issue #6702 has been updated by kommen (Dieter Komendera).


Just a short update from my side: Since my issue from comment #8 was mostly caused by bad .gemspec files from gems which didn't require 'date' before using it and most (all I know) have been fixed, I think this is not an issue any longer.

Though I still a agree with the original bug report, that this is a strange behaviour.

----------------------------------------
Bug #6702: Date should be either required or not
https://bugs.ruby-lang.org/issues/6702#change-41371

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


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/