Recursion introduction
From CSSEMediaWiki
(Difference between revisions)
(New page: When an operation need the method in one class to communicate to a method another class, then the interface of these two class (the method) should be named the same. If it happens to be th...) |
|||
| Line 1: | Line 1: | ||
| + | Giving related messages similar names, even if they have different parameters. | ||
| + | |||
When an operation need the method in one class to communicate to a method another class, then the interface of these two class (the method) should be named the same. If it happens to be the case where such two methods in the same class, then a logical recursive method is formed, this is defined as recursion introduction by Johnson and Foote. | When an operation need the method in one class to communicate to a method another class, then the interface of these two class (the method) should be named the same. If it happens to be the case where such two methods in the same class, then a logical recursive method is formed, this is defined as recursion introduction by Johnson and Foote. | ||
According to Johnson and Foote, the benefit of recursion introduction is to help programmer to decide what operation should be a method. | According to Johnson and Foote, the benefit of recursion introduction is to help programmer to decide what operation should be a method. | ||
Revision as of 01:09, 6 October 2008
Giving related messages similar names, even if they have different parameters.
When an operation need the method in one class to communicate to a method another class, then the interface of these two class (the method) should be named the same. If it happens to be the case where such two methods in the same class, then a logical recursive method is formed, this is defined as recursion introduction by Johnson and Foote.
According to Johnson and Foote, the benefit of recursion introduction is to help programmer to decide what operation should be a method.
