On Feb 8, 4:05 pm, [EMAIL PROTECTED] wrote:> > Composition is great when you know how largish classes are going to be > composed ahead of time and/or already have the pieces available in the form > of other classes you want to reuse. I use this fragment-by-multiple- > inheritance (I hesitate to call it a) pattern when I realize after a long > period of organic growth that a single-inheritance class has gotten too big. > It's often relatively easy to carve the class up into multiple related base > classes. The next step after that might be to morph those independent base > classes back into delegated attributes. > > Skip
I know, I just try to avoid the multiple inheritance transitional state and switch directly to the last step ;) M. Simionato -- http://mail.python.org/mailman/listinfo/python-list
