Hi.

Allen Wirfs-Brock wrote:

>  The Digitalk Smalltalk programming style guide had an item titled: "Never
>  use an array where an object will do".
>
>  The basic idea is that if you've reached the point where you need to
>  communicate some sort of heterogeneous aggregation then its time to define
>  a new class of object. It may seem like a heavyweight approach but down
>  stream you will most likely be glad you used a new class. Maintainers of
>  your code will certainly appreciate it.

This is exactly why I thought of Clusters. I got really surprised 
when all I had
to do was to reimplement #doesNotUnderstand:...

Andres.
Content-Type: application/x-unknown-content-type-st_auto_file;
  name="Cluster.st"
Content-Disposition: inline;
  filename="Cluster.st"

Attachment converted: Anon:Cluster.st 1 (????/----) (000079B4)