From: matz@... (Yukihiro Matsumoto)
Date: 2003-05-30T21:36:28+09:00
Subject: Re: Isn't NUM2UINT broken for 64-bit?

Hi,

In message "Re: Isn't NUM2UINT broken for 64-bit?"
    on 03/05/30, nobu.nokada@softhome.net <nobu.nokada@softhome.net> writes:
|
|At Fri, 30 May 2003 02:32:25 +0900,
|lyle@knology.net <lyle@knology.net> wrote:
|> The problem with this is that if you pass in a Ruby Integer that is greater
|> than the maximum value for a *signed* integer, the conversion fails, since
|> both rb_fix2int() and rb_num2int() compare their inputs to INT_MAX. I am
|> specifically seeing this problem for the value (2**32 - 1), which is in
|> range for unsigned integers, but I suppose it will happen for any Integer
|> greater than INT_MAX.
|> 
|> Is this a bug, or am I missing something?
|
|I guess it's a bug.

Commit the fix, please.

							matz.