Description:
------------
This report is a sequel to BUG #31943 and is in relation to BUG #32506 (posted by myself) most probably.

BUG #31943 was "solved" by reporter without a more detailed note, but nevertheless I think there's a misinterpretation of how and why abstract and static might be combined in an OOP-like system.

Or it is caused by non-virtual resolution of scope-reference self::... - then it is identical to BUG #32506.

Is it bad OOP to have constellations like this code below? Or is it just because of PHP5 not supporting virtual references? Well, in that case I prefer to have it on the wish list.


Best Regards,
Thomas Urban

Reproduce code:
---------------
abstract class a {
  static function test() {
    echo self::read();
  }
  abstract protected static function read();
}

class b extends a {
  protected static function read() {
    return "hello world!";
  }
}

b::test();


Expected result:
----------------
hello world!

Actual result:
--------------
Fatal error: Cannot call abstract method base::read() in ...