News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

PHP in Action:
Public constructors considered harmful
May 05, 2008 @ 10:21:33

According to the PHP in Action blog, public constructors can be hazardous to your (application's) health and should be replaced.

Everybody who writes object-oriented code knows about constructors. You need them so the program knows how to instantiate objects, right? And you especially need them when a lot of things have to be done while instantiating an object. [...] So why would I be skeptical of public constructors?

The solution, as he sees it, is to make a "constructor" that's actually called statically with parameters that returns an instance of the class it's in as well as performing the action. He argues that this can help make the code much more readable for some types of method calls.

1 comment voice your opinion now!
public constructor harmful replace private instance


blog comments powered by Disqus

Similar Posts

Paul Jones' Blog: Universal Constructor Sighting "In The Wild"

Larry Garfield's Blog: readfile() not considered harmful

Greg Beaver's Blog: Is anything working in PEAR?

Community News: Privates - Harmful or Useful? (Discussion)

Master Zend Framework: Howto Use Constructor Injection In ZF2


Community Events

Don't see your event here?
Let us know!


community interview part2 framework api laravel symfony2 podcast series voicesoftheelephpant language release configure performance example introduction conference php7 application opinion

All content copyright, 2015 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework