User Tools

Site Tools


principles:rule_of_explicitness

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
principles:rule_of_explicitness [2013-03-17 18:02] christianprinciples:rule_of_explicitness [2021-09-02 20:12] – old revision restored (2021-05-11 22:22) 65.21.179.175
Line 7: Line 7:
 ===== Context ===== ===== Context =====
 /* fill in contexts here: */ /* fill in contexts here: */
-  * [[contexts:Object-Oriented Design]] +  * [[contexts:Object-Oriented Design]] 
 +  * [[contexts:API Design]]
  
  
Line 17: Line 18:
 ===== Description ===== ===== Description =====
  
 +Solutions often differ in the level of explicitness. A feature can be implemented explicitly or it can be a side-effect of the implementation of another feature or a more general functionality. The same applies to module communication. A module can invoke another module directly or there can be various forms of indirections like events or observers.
  
 +RoE states that explicit solutions are better than implicit ones. Indirection, side-effects, configuration files, implicit conversions, etc. should be avoided.
 ===== Rationale ===== ===== Rationale =====
  
Line 94: Line 97:
  
  
-===== Example =====+===== Examples =====
  
  
principles/rule_of_explicitness.txt · Last modified: 2021-10-18 22:06 by christian