Duplicate code is one of the most pungent code smells. A rule that is often used is to re-structure code once it is duplicated in three or more places.
Common duplication problems, and corresponding solutions are:
| 1 | <?php |
||
| 17 | trait ViewsLoaderTrait |
||
| 18 | { |
||
| 19 | |||
| 20 | /** |
||
| 21 | * runViewsAutoLoader |
||
| 22 | */ |
||
| 23 | public function runViewsAutoLoader() |
||
| 28 | |||
| 29 | /** |
||
| 30 | * loadViewsFromContainers |
||
| 31 | */ |
||
| 32 | View Code Duplication | private function loadViewsFromContainers() |
|
| 43 | |||
| 44 | /** |
||
| 45 | * @param $directory |
||
| 46 | */ |
||
| 47 | private function loadViews($directory) |
||
| 51 | |||
| 52 | /** |
||
| 53 | * loadViewsFromPort |
||
| 54 | */ |
||
| 55 | private function loadViewsFromPort() |
||
| 62 | } |
||
| 63 |
PHP Analyzer performs a side-effects analysis of your code. A side-effect is basically anything that might be visible after the scope of the method is left.
Let’s take a look at an example:
If we look at the
getEmail()method, we can see that it has no side-effect. Whether you call this method or not, no future calls to other methods are affected by this. As such code as the following is useless:On the hand, if we look at the
setEmail(), this method _has_ side-effects. In the following case, we could not remove the method call: