These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | /** |
||
3 | * File-level block has no @package tag |
||
4 | * |
||
5 | * @copyright Copyright (c) 2010-2018 Mike van Riel / Naenius. (http://www.naenius.com) |
||
6 | */ |
||
7 | |||
8 | /** |
||
9 | * This class's block has a @package tag, though |
||
10 | * |
||
11 | * @package Package |
||
12 | * @copyright Copyright (c) 2010-2018 Mike van Riel / Naenius. (http://www.naenius.com) |
||
13 | */ |
||
14 | class NoPackageDocBlock |
||
0 ignored issues
–
show
|
|||
15 | { |
||
16 | } |
||
17 |
This check looks for classes that have been defined more than once.
If you can, we would recommend to use standard object-oriented programming techniques. For example, to avoid multiple types, it might make sense to create a common interface, and then multiple, different implementations for that interface.
This also has the side-effect of providing you with better IDE auto-completion, static analysis and also better OPCode caching from PHP.