Static classes in PHP via abstract keyword?

Question

According to the PHP manual, a class like this:

abstract class Example {}

cannot be instantiated. If I need a class without instance, e.g. for

Answer 1

From my understanding, a class without instance is something you shouldn't be using in an OOP program, because the whole (and sole) purpose of classes is to serve as blueprints for new objects. The only difference between Registry::$someValue and $GLOBALS['Registry_someValue'] is that the former looks 'fancier', but neither way is really object-oriented.

So, to answer your question, you don't want a "singleton class", you want a singleton object, optionally equipped with a factory method:

class Registry
{
    static $obj = null;

    protected function __construct() {
        ...
    }

    static function object() {
        return self::$obj ? self::$obj : self::$obj = new self;
    }
}

...

Registry::object()->someValue;

Clearly abstract won't work here.

Answer 2

What you describe is permitted by the PHP language, but it's not the intended usage of an abstract class. I wouldn't use static methods of an abstract class.

Here's the downside of doing that: Another developer could extend your abstract class and then instantiate an object, which is what you want to avoid. Example:

class MyRegistry extends AbstractRegistry { }
$reg = new MyRegistry();

True, you only need to worry about this if you're handing off your abstract class to another developer who won't comply with your intended usage, but that's why you would make the class a singleton too. An uncooperative developer can override a private constructor:

class Registry
{
  private function __construct() { }
}

class MyRegistry extends Registry
{
  public function __construct() { } // change private to public
}

If you were using this class yourself, you would simply remember not to instantiate the class. Then you wouldn't need either mechanism to prevent it. So since you're designing this to be used by others, you need some way to prevent those people from circumventing your intended usage.

So I offer these two possible alternatives:

1. Stick with the singleton pattern and make sure the constructor is also final so no one can extend your class and change the constructor to non-private:

   class Registry
   {
     private final function __construct() {
     }
   }
   

2. Make your Registry support both static and object usage:

   class Registry
   {
     protected static $reg = null;
   
     public static function getInstance() {
       if (self::$reg === null) {
         self::$reg = new Registry();
       }
       return self::$reg;
     }
   }
   

   Then you can call Registry::getInstance() statically, or you can call new Registry() if you want an object instance.

   Then you can do nifty things like store a new registry instance inside your global registry! :-)

   I implemented this as part of Zend Framework, in Zend_Registry

Answer 3

I wouldnt use an abstract class. Id use something more akin to a singleton with a protected/private constructor as you suggest. There should be very few static properties other than $instance which is the actual registry instance. Recently ive become a fan of Zend Frameworks typical pattern which is something like this:

class MyRegistry {

  protected static $instance = null;

  public function __construct($options = null)
  {
  }

  public static function setInstance(MyRegistry $instance)
  {
    self::$instance = $instance;
  }

  public static function getInstance()
  {
     if(null === self::$instance) {
        self::$instance = new self;
     }

     return self::$instance;
  }
}

This way you get a singleton essentially but you can inject a configured instance to use. This is handy for testing purposes and inheritance.

Answer 4

I would say it's a matter of coding habbits. When you think of an abstract class it is usually something you need to subclass in order to use. So declaring your class abstract is counter-intuitive.

Other than that is it just a matter of using self::$somevar in your methods if you make it abstract, rather than $this->somevar if you implement it as a singleton.