On Fri, Apr 1, 2011 at 5:13 PM, harrismh777 <harrismh...@charter.net> wrote: > Corollary 1)a The Class interface never encapsulates cruft.
Provably false. Even a well-designed interface, if it is asked to deal with a changing implementation and changing requirements, will eventually either acquire cruft, or be found too rigid to be of use. The only interface immune to this is the transparent interface (effectively: "just package up the parameters in a single string and pass it through"), which isn't really an interface at all, it just exposes something else. In everything else, cruft is a reality that must be dealt with. Chris Angelico -- http://mail.python.org/mailman/listinfo/python-list
