Description:
------------
When running in CLI with strict errors enabled & display_errors turned on, PHP does not produce all strict warnings reliably.

Some, like:

"Strict Standards: Non-static method b::init() should not be called statically in /usr/home/tomek/test.php on line 25"

is 100% reproducible.

Others, like:

"Strict Standards: Declaration of b::init() should be compatible with that of a::init() in /usr/home/tomek/test.php on line 8"

are not reproducible using the code attached. Swapping the class declarations, however, makes the warning appear (ie. "class b extends a" goes first, and only then define "class a").

Please note that this is the *only* change required for it to appear. 

This is very similar to bug #46851.

Reproduce code:
---------------
<?php

error_reporting(E_ALL | E_STRICT);

ini_set('display_errors', 'On');
ini_set('log_errors', 'Off');

class a
{
  public function init($v) {}
}

class b extends a
{
  public function init() {}
}

b::init();

Expected result:
----------------
Strict Standards: Declaration of b::init() should be compatible with that of a::init() in /usr/home/tomek/test.php on line 8

Strict Standards: Non-static method b::init() should not be called statically in /usr/home/tomek/test.php on line 19


Actual result:
--------------
Strict Standards: Non-static method b::init() should not be called statically in /usr/home/tomek/test.php on line 19