1 | <?php |
||
10 | Class Sensei_Twentyfifteen extends Sensei__S { |
||
11 | |||
12 | /** |
||
13 | * Output opening wrappers |
||
14 | * @since 1.9.0 |
||
15 | */ |
||
16 | public function wrapper_start(){ |
||
25 | |||
26 | |||
27 | /** |
||
28 | * Output the style for the |
||
29 | * twenty fifteen theme integration. |
||
30 | * |
||
31 | * @since 1.9.0 |
||
32 | */ |
||
33 | private function print_styles(){?> |
||
111 | |||
112 | } // end class |
||
113 |
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: