From: Yukihiro Matsumoto <matz@...>
Date: 2010-03-03T16:48:48+09:00
Subject: [ruby-core:28437] Re: [Bug #2830] Some methods raise ArgumentError instead of TypeError

Hi,

In message "Re: [ruby-core:28395] [Bug #2830] Some methods raise ArgumentError instead of TypeError"
    on Tue, 2 Mar 2010 13:45:11 +0900, Marc-Andre Lafortune <redmine@ruby-lang.org> writes:

|Some methods of Ruby 1.9 expect integers/reals and call internally nurat_int_value/nurat_int_check. These functions raise an ArgumentError when the argument is not an Integer, instead of a TypeError.
|Unless there is objection, I will commit the following patch (and fix RubySpec):

Go ahead.  I am thinking of making TypeError subclass of
ArgumentError, since every TypeError should occur in relation to any
argument.  How do you (guys) think?

							matz.