Aktuelle Änderungen Printable View Änderungen Bearbeiten
LessCode > LexerAndParser > Linux > LiquidInformation > LispEnlightenment > LispExtensions > LispHacks > LispInOtherLanguages > LispMachines > LispOnSpeed > LispOrScheme > LispSprache > Lisp > LispTreasury > LiveCoding > LoC > LooseCouplingClear TrailLoose coupling describes an approach where integration interfaces are developed with minimal assumptions between the sending/receiving parties, thus reducing the risk that a change in one application/module will force a change in another application/module.
Loose coupling describes a resilient relationship between two or more systems or organizations with some kind of exchange relationship. Each end of the transaction makes its requirements explicit and makes few assumptions about the other end.
loosely coupled is an attribute of systems, referring to an approach to designing interfaces across modules to reduce the interdependencies across modules or components – in particular, reducing the risk that changes within one module will create unanticipated changes within other modules. This approach specifically seeks to increase flexibility in adding modules, replacing modules and changing operations within individual modules. [1]
the situation where one module depends on another module having some special state, or set of string literals, but where the compiler doesn’t know.
In some ways, this [doing reflection] goes against my usual principles of coding. Any typos won't be caught until runtime. If you change the constructors for MyClass, the compiler won't catch them for you. And it doesn't really decrease the coupling; it just hides the coupling from the compiler and class loader.
In software engineering terms, this is probably worse code rather than better, but it solves certain problems more easily than the alternative, which is to keep several different versions of the program with different capabilities.[2]