Initializing properties in PHP

user_409279 0
Viewed 5968

While I'm led to believe its likely just a design choice, is there any advantage to initializing properties in PHP to an explicit null?

As a force of habit I find myself doing:

// ...
protected $_foo = null;
protected $_bar = null;
protected $_baz = null;
// ...

Of course, under circumstances where actual data is intended to be present at object instantiation, there is purpose:

// ...
protected $_array = array('a', 'b', 'c');
protected $_boolean = true;
// ...

Is omission of a null initialization value completely functionally equivalent to inclusion of a null initialization? Are there any other caveats? Also, unless a property is type-checked before any assignments would be made, initialization to an empty array seems like similar situation (and I find myself doing that constantly)

php
5 Answers

PHP 7.4 introduced a new feature called "typed properties" which adds the existing PHP type system to class properties. This means that you can now enforce which types a property has without having to encapsulate it in an object.

Typed properties are a very useful feature, however, typed properties without a default value have a new state: uninitialized. And if they're accessed before being initialised, you'll run into a Typed property must not be accessed before initialization error.

So the correct answer to OPs question if you're using PHP 7.4+ is yes, it does matter whether or not you explicitly initialise your class variables and the following two lines are not equivalent any more:

protected int $_foo = null;
protected int $_foo; // The default value in PHP 7.4+ is now uninitialized, not NULL

Further reading (no relation): https://madewithlove.com/typed-property-must-not-be-accessed-before-initialization/

user_4290710
Related