>
>
> What I want to say. I've started to think about prototype-based  
> programming
> from Io and JavaScript. My very first impression was "I create  
> objects, I
> clone objects, that's all". But further I've found, the more  
> experienced
> people think about prototype-based as "each object has it's  
> prototype" first
> of all (which becames "object's prototype processes all unknown  
> signals",
> "object's prototype can be changed" and even Io's "prototype  
> defines lexical
> scope").
>
> It seems prototype.rb now does something like "my first  
> impression", not
> "prototype-based entirely".
>
> Am I wrong?

on second thought it's a hybrid.  in prototype.rb's case you merely  
have to consider each object's class as it's 'prototype' - all  
methods are defined/intercepted there.  this a symptom of the fact  
that ruby only allows method definitions to reside in modules.

-a
--
we can deny everything, except that we have the possibility of being  
better. simply reflect on that.
h.h. the 14th dalai lama