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

PHPMaster.com: From Zero to Cloud: Setting up an EC2 Sandbox, Part 3

CodeSnipers.com: Embarking on PHP5 Objects

PHPit.net: Having fun with PHP\'s output buffer

VG Tech: Comparing Your Privates in PHP

Ralph Schindler's Blog: PHP Constructor Best Practices And The Prototype Pattern


Community Events





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


install introduction framework language series configure laravel refactor code wordpress interview unittest podcast testing threedevsandamaybe developer community opinion release list

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