Option-operand separation
From CSSEMediaWiki
(Difference between revisions)
BenMcDonald (Talk | contribs) (New page: Methods containing operands, necessary augments, should be separated from methods containing options, augments not vital to the method. Justification: * Methods containing options will ch...) |
m (Reverted edits by Ebybymic (Talk); changed back to last version by BenMcDonald) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
Justification: | Justification: | ||
* Methods containing options will change more frequently than methods containing operands and so should be isolated. | * Methods containing options will change more frequently than methods containing operands and so should be isolated. | ||
| − | * Makes code clearer and | + | * Makes code clearer and removes hidden, hard to find in code method arguments. |
| − | * Removes the need for method polymorphism, a practise that makes code hard to read | + | * Removes the need for method polymorphism, a practise that makes code hard to read. |
Devised by [[Bertrand Meyer]] | Devised by [[Bertrand Meyer]] | ||
Latest revision as of 03:08, 25 November 2010
Methods containing operands, necessary augments, should be separated from methods containing options, augments not vital to the method.
Justification:
- Methods containing options will change more frequently than methods containing operands and so should be isolated.
- Makes code clearer and removes hidden, hard to find in code method arguments.
- Removes the need for method polymorphism, a practise that makes code hard to read.
Devised by Bertrand Meyer
