Sounds like you’d be better served by a singleton rather than a bunch of static methods class Singleton { /** * * @var Singleton */ private static $instance; private function __construct() { // Your “heavy” initialization stuff here } public static function getInstance() { if ( is_null( self::$instance ) ) { self::$instance = new self(); … Read more
Static initializers are useful as cletus mentioned and I use them in the same manner. If you have a static variable that is to be initialized when the class is loaded, then a static initializer is the way to go, especially as it allows you to do a complex initialization and still have the static … Read more
This question was the subject of my blog on September 20th 2010. Josh and Chad’s answers (“they add no value so why require them?” and “to eliminate redundancy”) are basically correct. To flesh that out a bit more: The feature of allowing you to elide the argument list as part of the “larger feature” of … Read more
Just add to your FacebookLoginStrategy: public init() {} As long as you do not implement init() explicitly, it is marked as internal by default. You need to overwrite that permission level to be able to instantiate from outside your framework.
To get the equivalent of a static constructor, you need to write a separate ordinary class to hold the static data and then make a static instance of that ordinary class. class StaticStuff { std::vector<char> letters_; public: StaticStuff() { for (char c=”a”; c <= ‘z’; c++) letters_.push_back(c); } // provide some way to get at … Read more