| 1 | <?php |
||
| 19 | class DoctrineObjectHydratorLocatorFactory implements FactoryInterface |
||
| 20 | { |
||
| 21 | /** |
||
| 22 | * @param ServiceLocatorInterface $serviceLocator |
||
| 23 | * |
||
| 24 | * @return DoctrineObjectHydratorLocator |
||
| 25 | * |
||
| 26 | * @throws \Zend\ServiceManager\Exception\ServiceNotFoundException |
||
| 27 | */ |
||
| 28 | public function createService(ServiceLocatorInterface $serviceLocator) |
||
| 44 | } |
||
| 45 |
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: