From: Josef 'Jupp' SCHUGT <jupp@...>
Date: 2003-12-18T09:30:04+09:00
Subject: Re: 42.type and TypeError or 42.class and ClassError

Hi!

* Ara.T.Howard; 2003-12-17, 19:21 UTC:
> why has #type been deprecated?

That can be answered by quoting Gamma, Helm, Johnson Vilissides,
'Design Patterns - Elements of Reusable Object-Oriented Software',
page 16 (bottom):

    It's important to understand the difference between an object's
    /class/ and its /type/.

    An object's class defines how the object is implemented. The
    class defines the object's internal state and the implementation
    of its operations. In contrast, an object's type only refers to
    its interface---the set of requests to which it can respond. An
    object can have many types, and objects of different classes can
    have the same type.

I strongly recommend that book - it is great. It is worth its price
of 54.99 USD.

Josef 'Jupp' SCHUGT
-- 
http://oss.erdfunkstelle.de/ruby/    -     German comp.lang.ruby-FAQ
http://rubyforge.org/users/jupp/     -     Ruby projects at Rubyforge
._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._.
Windows are best when they are "unseen"   --   Chet Noll 27 Oct 2000