Hi,

2010/7/31 Roger Neel <redmine@ruby-lang.org>:

I do see your point, but we can't change the behavior because of
compatibility reason. I recommend you to propose new method for
the new behavior, or to wait for 2.0.