From: "David A. Black" <dblack@...>
Date: 2005-01-31T22:41:24+09:00
Subject: Re: Ten Things Every Java Programmer Should Know About Ruby

--927295978-1771484319-1107178871=:17105
Content-Type: MULTIPART/MIXED; BOUNDARY="927295978-1771484319-1107178871=:17105"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--927295978-1771484319-1107178871=:17105
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi --

On Sun, 30 Jan 2005, E S wrote:

>> L=E4hett=E4j=E4: Navindra Umanee <navindra@cs.mcgill.ca>
>> Aihe: Re: Ten Things Every Java Programmer Should Know About Ruby
>
>> An object in Ruby may even change its type from one moment to the
>> other.  A Socket object may suddenly become a File object.
>
> No, a label for a Socket object (e.g. 'foo' in 'foo =3D Socket.new') may
> point to a different type of an object. The object itself doesn't
> change. This is a really important bit.

Also, an object's type (as opposed to its class) can change
dynamically:

    a =3D "hi"
    def a.x; puts "I'm not like other strings!"; end

or

    class C
      def self.some_class_method
        puts "I am no longer the same type as a brand-new Class object."
      end
    end

etc.


David

--=20
David A. Black
dblack@wobblini.net
--927295978-1771484319-1107178871=:17105--
--927295978-1771484319-1107178871=:17105--