Wejn wrote:
> $ ruby -e 'p Range.new(1,4).type'
> Range
> $ ruby -e 'p (1..4).type'
> 1..4
> 
> Well, what's wrong with the latter?

It appears to be an issue of precedence. Typing this in irb, I get:
  irb(main):001:0> p (1..4).type
  1..4
  NilClass
....suggesting that the type call binds to the result of the p call. This
works as expected on 1.7.2, but you really should write it
p((1..4).type) to remove ambiguity.


> raises exception for 'uid = 997'
.... 
> $ ruby -v
> ruby 1.6.7 (2002-06-30) [i686-linux]

Unable to reproduce this problem on both
ruby 1.6.6 (2001-12-26) [i586-linux-gnu] and
ruby 1.7.2 (2002-07-13) [i686-linux] so I can't help you on that one,
sorry...

-- 
(\[ Kent Dahl ]/)_    _~_    __[ http://www.stud.ntnu.no/~kentda/ ]___/~
 ))\_student_/((  \__d L b__/  NTNU - graduate engineering - 4. year  )
( \__\_õüõß/__/ ) _)Industrial economics and technological management(
 \____/_öß\____/ (____engineering.discipline_=_Computer::Technology___)