CodeIgniter helpful hints

[eluser]xwero[/eluser]
[quote author="CodeIgniter" date="1203454058"]@xwero about reply #18: I tend to disagree as I think absolutely the opposite.

The fact of the matter is that you need Base controllers, otherwise, it implies that your code is very repetitive. Some controllers share the same behavior, especially at initialization, it is perfectly natural to group these behaviors in a parent class. This is exactly what inheritance is about. The MY_Controller.php file is a convenience file provided to do exactly that. You don't have to name your extended controller MY_Controller for it to be available. I guess people do it for consistency, but you can as well name it 'Base' and create other Parent classes in the same file with other arbitrary names. They still will be available to your application's controllers.
[/quote]
I'm not saying you don't need base controllers. I'm saying break up your files as much as possible. When there are changes later you can limit the impact of the changes to the files that need the change. For instance:

Code:

// my_controller.php
My_controller extends Controller{}
// admin_controller.php
include('my_controller.php');
Admin_controller extends MY_Controller{}
// users.php
include('admin_controller.php');
Users extends Admin_Controller{}
// blog.php
include('admin_controller.php');
Blog extends Admin_Controller{}
// rss.php
include('admin_controller.php');
Rss extends Admin_Controller{}

You need to make changes to the admin_controller that only affect the blog and rss child classes. You only have to create another file and change the include for those child classes. If there is an error in the code it only affects those child classes.

If you put the new my_controller extended class in the my_controller file all children will be affected if there is an error.