Musings about modularity and programming in the large
bert at freudenbergs.de
Fri Jan 25 14:56:35 UTC 2008
On Jan 25, 2008, at 15:48 , itsme213 wrote:
> "Igor Stasenko" <siguctua at gmail.com> wrote in message
>>> Would something like that be relevant to not breaking the
>>> inheritance of
>>> metaclass hierarchy?
>> I heard about this a while ago. IIRC perl having per-object behavior
>> But this can be easily made , when object model is prototype based
>> And in ST we having a class-based model.
>> Btw, can you show us a 'killer' use case of such language feature,
>> which shows great benefit comparing to class-based model? I'm very
>> intrigued. :)
> Ruby is a class-based, not a prototype-based language. It allows
> customization by silently inserting a per-object class only where
> but does not go the next step with the required "self" magic of a
> prototype-based language. Smalltalk can do this easily (perhaps not as
> conveniently as Ruby) e.g. Avi has a package on SqueakSource called
> Prototype, I think.
FWIW this is exactly what Etoys does (which implements a fat object
model on top of Squeak).
- Bert -
More information about the Squeak-dev