Mark Summerfield writes:
> Sometimes I want to spread a class over multiple files.
When I run into such a use case, I use (multiple) inheritance --
with "mixin class"es.
Each "mixin class" handles some important aspect and is only loosely
coupled with maybe a common b
Sometimes I want to spread a class over multiple files.
My primary use case is when I create a "Model" class to reflect an entire SQL
database. I want a model instance to provide a single point of access to the
database, but the database has many tables each requiring its own met
