Conditions | 2 |
Paths | 2 |
Total Lines | 10 |
Code Lines | 6 |
Lines | 0 |
Ratio | 0 % |
Changes | 0 |
1 | <?php |
||
39 | private function evalClass(ClassMetadata $class) |
||
40 | { |
||
41 | $class->setName($class->getName() . '__PROXY__'); |
||
42 | while (class_exists($this->getCanonicalClassName($class))) { |
||
43 | $class->setName($class->getName() . mt_rand(0, 999)); |
||
44 | } |
||
45 | |||
46 | $result = @eval((string)$class) !== false; |
||
47 | return $result; |
||
48 | } |
||
49 | |||
73 |
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: