Subj : Re: Polymorphism sucks [Was: Paradigms which way to go?] To : comp.programming,comp.object From : Chris Sonnack Date : Thu Jun 30 2005 06:44 pm topmind writes: >>> Copy-and-paste actually *reduces* coupling because it lets things be >>> independent, for example. Thus, if reducing coupling is always good, >>> then copy-and-paste is always good. >> >> It may appear to reduce coupling, but as has been said, it creates an >> invisible (to the source) web of coupling that needs to be documented >> and maintained by the developer. > > Yes, but that is a nebulous form of "coupling". Which is the worst kind! Much harder to maintain. > Robert Martin implied that "coupling" was sure-shot metric that by > itself would guide decisions. No, that was your willful misinterpretation of what he said. There are no sure-fire metrics, the Universal Answer to any computing question is always, "It Depends." > Note that I was not promoting copy-and-paste above. I was only > exploring it's relationship to Robert's view of "coupling". Coupling is usually to be avoided as much as possible. Invisible coupling that depends on separate documentation or programmer memory is the worst kind. There's nothing inconsistant with what Robert said. -- |_ CJSonnack _____________| How's my programming? | |_ http://www.Sonnack.com/ ___________________| Call: 1-800-DEV-NULL | |_____________________________________________|_______________________| .