Sub sub-folders not working in controllers

[eluser]adamp1[/eluser]
The problem with not having nested sub folders is you normally have one to separate admin controllers from public controllers. Now you can have more sub folders like this 'admin' one for the public area, but you can't have any for the admin area (since where already 1 folder deep). Which means all your admin controllers must be in a single folder. Now say I have a hugely complex backend and its spread across many many controllers. I don't want all these in a single folder, yes it could work but its horrid to work with.

So a little example, if you want the following the current setup is fine:

Code:

/admin
    users.php
    manage.php
  home.php
  view.php

But if I have many controllers which are all related, but are so individually complex I don't want them in a single controller we end up with this. (Lets say each controller is 1000 lines long and each have their own add/edit/delete option)

Code:

/admin
    package1_subcontroller1.php
    package1_subcontroller2.php
    package1_subcontroller3.php
    package1_subcontroller4.php
    package2_subcontroller1.php
    package2_subcontroller2.php
    package2_subcontroller3.php
    package2_subcontroller4.php
  home.php
  view.php

Now as you can see that's not very nice. Now some say use routes, but using routes that's another part of the program to break and update if I want to add something. Why add more complexity if you can use folders to do the job? The way CI is setup at the moment for controllers is crazy to me atm.

One last thing, if the change proposed in this was implemented it wouldn't break any old code, so if you didn't want to use it, you don't have to.post