Description:
------------
The issue is pretty simple I've explained this problem before, I'm unsure why it hasn't been addressed - it's a design flaw and violates basic principles of what you'd expect from an OOP language.

Consider a static function in a base class, and a class that inherits from the above. In such a static function, self:: always refers to the class where the code was declared. That is wrong, it should be relative to the class the code was called from. It makes it impossible to have seperate variables in sub-classes sharing the same code.

It is easier watching the example, it speaks for itself. When "test()" runs, on the second call, it should be running within context of ClassB, not ClassA.

This is related to bug #28442, which was apparently ignored. Can someone at least explain what is the reasoning behind it working like that? I don't want to sound rude, but I know how it works, the distinctions between public and private, please don't patronize me (again). :)

Reproduce code:
---------------
class ClassA
{
   private static $base    = "Variable from ClassA";
   static function   test()
   {
      print( self::$base . "\n" );
   }
}

class ClassB extends ClassA
{
   private static $base = "Variable from ClassB";
}

ClassA::test();
ClassB::test();


Expected result:
----------------
Variable from ClassA
Variable from ClassB

Actual result:
--------------
Variable from ClassA
Variable from ClassA