From: Robert Dober <robert.dober@...>
Date: 2007-06-27T00:30:55+09:00
Subject: Re: Error in ancestor?

On 6/26/07, dblack@wobblini.net <dblack@wobblini.net> wrote:

> The thing is, there's one big difference that's not just a matter of
> implementation: singleton classes of Class objects are the only ones
> that can actually be called by more than one object (the class, plus
> its descendants).
I am definitely lost here, what do you mean by "can be called", their
methods of course, ok so that is exactly what I meant, it is the
"outside world" that makes the difference.
It is not the "fault" of the Singleton Class that it does not inherit
from Module, could we imagine the following e.g.:

s="a"
t=class<<s
   def hi; 42 end
   self
end
c = Class.new{ include t }

BTW I wanted just to be sure that this and some other tricks do not
work and they don't :-(
But Ruby threw a "Virtual Class" to me, actually did we discuss this
name?, I quite like it.

Cheers
Robert


-- 
You see things; and you say Why?
But I dream things that never were; and I say Why not?
-- George Bernard Shaw