onoi /
tesa
| Conditions | 1 |
| Paths | 1 |
| Total Lines | 11 |
| Code Lines | 7 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
| 1 | <?php |
||
| 18 | public function testCanConstruct() { |
||
| 19 | |||
| 20 | $tokenizer = $this->getMockBuilder( '\Onoi\Tesa\Tokenizer\Tokenizer' ) |
||
| 21 | ->disableOriginalConstructor() |
||
| 22 | ->getMockForAbstractClass(); |
||
| 23 | |||
| 24 | $this->assertInstanceOf( |
||
| 25 | '\Onoi\Tesa\Tokenizer\JaTinySegmenterTokenizer', |
||
| 26 | new JaTinySegmenterTokenizer( $tokenizer ) |
||
| 27 | ); |
||
| 28 | } |
||
| 29 | |||
| 192 |
Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code.
Let’s take a look at an example:
As you can see in this example, the array
$myArrayis initialized the first time when the foreach loop is entered. You can also see that the value of thebarkey is only written conditionally; thus, its value might result from a previous iteration.This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization $myArray = array() either outside or inside the foreach loop.