From: Jamis Buck <jgb3@...>
Date: 2003-12-18T02:34:21+09:00
Subject: Re: 42.type and TypeError or 42.class and ClassError

Ara.T.Howard wrote:

>personally i don't see the problem with type even if it isn't _totally_ in
>line with the 'ruby way' of thinking - it's meaning is perfectly clear in code
>IMHO.
>  
>

I have no idea if this is one of the reasons #type has been deprecated, 
but I've always disliked it because there have been many times that I 
wanted to create a method of my own, called #type.  In those cases, I 
either had to alias the original #type method, or simply live without it.

-- 
Jamis Buck
jgb3@email.byu.edu

ruby -h | ruby -e 'a=[];readlines.join.scan(/-(.)\[e|Kk(\S*)|le.l(..)e|#!(\S*)/) {|r| a << r.compact.first };puts "\n>#{a.join(%q/ /)}<\n\n"'