Calling methods at object creation via constructor performance effect PHP

Question

My question is what is the best way in terms of performance. For example in the application bootstrap process i have a class

<?php 
class Application
{
    public function __construct()
    {
        $this->setErrorHandler();
        $this->setDatabase();
        $this->sessionHandler();
        $this->disptachRequest();
    }

}
$app = new Application;

Is this a good approach or i should call these methods separately from the variable that holds the object?

I have set those function to private actually that is why i am calling them in constructor. Need guidance if this is good or bad?

Do all of those methods really take no arguments, or did you just leave them out to simplify the code for the question? — Don't Panic
– Don't Panic, Commented Aug 7, 2015 at 21:58

Fabian Schmengler · Accepted Answer · 2015-08-29 09:30:16Z

1

There is nothing inherently bad in it.

For performance, the question is, if all the calls are necessary in all cases. if not, you could defer them and execute them only if needed (this is called lazy loading)

For proper object oriented design the question is if the Application class and all its methods serve a common single responsibility. If not, break it down into smaller classes.

answered Aug 29, 2015 at 9:30

Fabian Schmengler

24.6k9 gold badges82 silver badges114 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Calling methods at object creation via constructor performance effect PHP

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related