These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | /** |
||
4 | * @license LGPLv3, http://opensource.org/licenses/LGPL-3.0 |
||
5 | * @copyright Aimeos (aimeos.org), 2017 |
||
6 | * @package MW |
||
7 | * @subpackage Process |
||
8 | */ |
||
9 | |||
10 | |||
11 | namespace Aimeos\MW\Process\Decorator; |
||
12 | |||
13 | |||
14 | /** |
||
15 | * Common interface for parallel processing decorators |
||
16 | * |
||
17 | * @package MW |
||
18 | * @subpackage Process |
||
19 | */ |
||
20 | interface Iface extends \Aimeos\MW\Process\Iface |
||
21 | { |
||
22 | /** |
||
23 | * Initializes the object |
||
24 | * |
||
25 | * @param Aimeos\MW\Process\Iface $object Parallel processing object |
||
26 | */ |
||
27 | public function __construct( \Aimeos\MW\Process\Iface $object ); |
||
0 ignored issues
–
show
|
|||
28 | } |
For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a
@return
doc comment to communicate to implementors of these methods what they are expected to return.