From: "Ara.T.Howard" <ahoward@...>
Date: 2003-12-18T01:47:00+09:00
Subject: 42.type and TypeError or 42.class and ClassError



why has #type been deprecated?  i don't really like using Object#class since
it always conflicts with the keyword 'class'; eg.  you have to

  self.class.method

instead of the cleaner

  type.method

also, having #class prefered over #type, but TypeError as the error definitely
violated POLS.  we should at least have ClassError if #class is the way to go.

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.

-a
-- 

ATTN: please update your address books with address below!

===============================================================================
| EMAIL   :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
| PHONE   :: 303.497.6469
| ADDRESS :: E/GC2 325 Broadway, Boulder, CO 80305-3328
| STP     :: http://www.ngdc.noaa.gov/stp/
| NGDC    :: http://www.ngdc.noaa.gov/
| NESDIS  :: http://www.nesdis.noaa.gov/
| NOAA    :: http://www.noaa.gov/
| US DOC  :: http://www.commerce.gov/
|
| The difference between art and science is that science is what we
| understand well enough to explain to a computer.  
| Art is everything else.  
|   -- Donald Knuth, "Discover"
|
| /bin/sh -c 'for l in ruby perl;do $l -e "print \"\x3a\x2d\x29\x0a\"";done' 
===============================================================================