walter / mwsewall.com wrote:
> That would work in this simple example...  What I find is that I tend 
> to perform similar tasks on groups of Objects.  

I use object.extend(Module) a bit, to add aspect-oriented features to
existing objects in my code generator. The generator reads a schema
file creating various kinds of objects, and then, when running one
of (for example) the C# generators (we have 4), I extend the schema
objects with knowledge of C#. Same thing for C++, SQL, documentation,
etc - so the generators don't duplicate code or require shared
functions, and the knowledge of all generatable languages isn't built
into the schema objects all the time.

> Ruby has such beautiful Array functionality that I find I always end 
> up wanting to use it in my customized subclasses.

Can't you get much of what you want my mixing-in Enumerable?