Sometimes we have Models and Controllers where the function __construct() just doesn't do anything, but is sitting on the top of all the methods in CodeIgniter's models and controllers. A lot of CodeIgniter books teach it that way. Following is the example of a __construct(), where it isn't doing anything, and if you remove it the application doesn't break. <?phpdefined('BASEPATH') OR exit('No direct script access allowed');class Register_model extends CI_Model {  public function __construct()  {    parent::__construct();  }  public function register_user($data)  {    return ($this->db->insert('users', $data)) ? true : false;  }}/* End of file Register_model.php *//* Location: ./application/models/Register_model.php */If we instead use it like as follow (without __construct()), the application won't break.<?phpdefined('BASEPATH') OR exit('No direct script access allowed');class Register_model extends CI_Model {  public function register_user($data)  {    return ($this->db->insert('users', $data)) ? true : false;  }}/* End of file Register_model.php *//* Location: ./application/models/Register_model.php */So what is better (or good practice) in this case, to use a __construct(), or not to use it?
Is it always better to use __construct() in CodeIgniter's Models and Views, even if it's not needed?
object oriented;php;mvc;constructors;codeigniter