From: matz@... (Yukihiro Matsumoto)
Date: 2003-12-18T02:42:46+09:00
Subject: Re: 42.type and TypeError or 42.class and ClassError

Hi,

In message "42.type and TypeError or 42.class and ClassError"
    on 03/12/18, "Ara.T.Howard" <ahoward@ngdc.noaa.gov> writes:

|why has #type been deprecated?

Because type has broader meaning and tends to introduce confusion.
Besides I wanted to save the word "type" for something based on method
signature.

|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.

Since type is broader concept that includes class, I think an error
caused by instances of wrong class is a part of type error.

							matz.