php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #62320 Abstract static property?
Submitted: 2012-06-14 07:04 UTC Modified: 2021-07-27 11:13 UTC
Votes:5
Avg. Score:4.0 ± 1.5
Reproduced:4 of 5 (80.0%)
Same Version:3 (75.0%)
Same OS:3 (75.0%)
From: techlivezheng at gmail dot com Assigned:
Status: Suspended Package: Scripting Engine problem
PHP Version: 5.4.3 OS: Linux
Private report: No CVE-ID: None
 [2012-06-14 07:04 UTC] techlivezheng at gmail dot com
Description:
------------
As we have "late static bindings" now, would it be reasonable to have a "abstract static property"?

See the bellow example.

abstract class A {
    //If this could be declared as abstract to make 
    //the subclass have to redeclare it in order to
    //have it own $mTest to use.
    //If $mTest is not declared in one subclass, it would
    //change the $mTest of A which is shared by many 
    //subclasses, some unexpected things would happen.
    //The design is to make each subclass have its own
    //$mTest to use and it has to be existed.
    //$mTest in A is just for a skeleton purpose, even should
    //not be assigned a value.
    static $mTest;

    static function setTest($value) {
        static::$mTest = $value;
    }

    static function DumpTest () {
        echo 'static:' . static::$mTest . "\n";
        echo 'A-self:' . self::$mTest . "\n";
    }
}

class B extends A {
    static function DumpTest () {
        parent::DumpTest();
        echo 'B-self:' . self::$mTest . "\n";
        echo 'B-parent:' . parent::$mTest . "\n";
    }
}

class C extends A {
    static $mTest;
    static function DumpTest () {
        parent::DumpTest();
        echo 'C-self:' . self::$mTest . "\n";
        echo 'C-parent:' . parent::$mTest . "\n";
    }
}

class D extends C {
    static $mTest;
    static function DumpTest () {
        parent::DumpTest();
        echo 'D-self:' . self::$mTest . "\n";
        echo 'D-parent:' . parent::$mTest . "\n";
    }
}

B::setTest('test1');//This will change the $mStorages of class A
B::DumpTest();
//static:test1
//A-self:test1
//B-self:test1
//B-parent:test1
C::setTest('test2');
C::DumpTest();
//static:test2
//A-self:test1
//C-self:test2
//C-parent:test1
D::setTest('test3');
D::DumpTest();
static:test3
//A-self:test1
//C-self:test2
//C-parent:test1
//D-self:test3
//D-parent:test2


Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2012-10-26 16:06 UTC] dagguh at gmail dot com
Late Static Binding is a failed concept and should be avoided in all cases.
There is no such thing as static inheritance. Static members of a class belong to 
this class and this class only.

Just use the regular instance methods and regular inheritance.
Your code will be more testable, extensible and modular.

Please close this issue as "won't fix".
 [2013-01-08 23:42 UTC] jon at langevin dot me
Very valid issue, please correct. Just because users such as "dagguh" can't 
figure out how to make LSB work, that doesn't mean it's a failed concept.

Great feature, it's just missing the needed abstract static functionality.
 [2021-07-27 11:13 UTC] cmb@php.net
-Status: Open +Status: Suspended
 [2021-07-27 11:13 UTC] cmb@php.net
Please pursue the RFC process[1].  For the time being, I suspend
this ticket.

[1] <https://wiki.php.net/rfc/howto>
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Oct 31 23:01:28 2024 UTC