From: Mathieu Bouchard <matju@...>
Date: 2001-06-29T06:13:08+09:00
Subject: [ruby-talk:17033] Re: Something strange with Ruby's inheritance mechanism


On Tue, 26 Jun 2001, Eric Jacoboni wrote:
> 
> That's exactly my problem : A is a subset of B. A subset of objects: a
> A object is always a B object, the opposite is not necessary true. My
> first post was about the lack of this concept in Ruby: dynamic typing
> prevents it as an A object may become, say, an Integer. As beginner in
> Ruby, the surprise comes from the fact that the OOP is ok as long as
> we stay at the class level but disappears when we come to instances
> (object) because of dynamic typing.

Unlike SmallTalk, Ruby does not have Object#become, or anything. You can't
change the class of an object. I think you may not be distinguishing
variables from objects.

matju