[PATCH] for [ #1823 ] NUM2UINT and rb_num2ull do not rase RangeError for negative Fixnum

All,

I submitted bug 1823 while anonymous CVS was unavailable; however, now
that I can access CVS, I went ahead and applied the fix that I proposed
and it works well with my extension.

To summarize, the problem is that NUM2UINT and rb_num2ull accept
negative Fixnum's while unsigned ints and long longs can not be less
than zero. For numbers that are larger than the largest unsigned int or
long long these methods correctly raise a RangeError. For the sake of
consistency and correctness they should raise a RangeError when the
value is less than 0 as well.

It is simple enough to work around this problem in my extension;
however, the fact that everything behaves so predictably is one of the
aspects of writing Ruby extensions that impresses me the most. I am just
getting started with Ruby and writing extensions, and this is the only
problem to date.

Regards,
Michael Schonberg
[e-mail]